janusgraph-dev@lists.lfaidata.foundation | DynamoDB storage backend

Home Messages Hashtags Subgroups Calendar

Date Date 1 - 10 of 10

DynamoDB storage backend

mcha...@... #493 In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen?
More
Robert Dale <rob...@...> #494 It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale toggle quoted message Show quoted text On Thu, Dec 7, 2017 at 1:16 PM, <mcha...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
mcha...@... #495 I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. toggle quoted message Show quoted text On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
Stephen Mallette <spmal...@...> #497 That's an interesting statement....could you elaborate? toggle quoted message Show quoted text On Fri, Dec 8, 2017 at 11:39 AM, <mcha...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
mcha...@... #496 Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures. They are "essentially" unlimited in the amount of data, or cluster size. Neptune - as of today - is limited to 64TB of data. it has one write master (limiting write capacity) and up to 15 read replicas (liming read capacity). they project that means 100B relations in graph DB - subject to size and number of string properties toggle quoted message Show quoted text On Friday, December 8, 2017 at 12:20:23 PM UTC-5, Stephen Mallette wrote: That's an interesting statement....could you elaborate? On Fri, Dec 8, 2017 at 11:39 AM, <mc...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
Henry Saputra <henry....@...> #561 Sorry to follow up on old thread, anyone from AWS could chime whether Neptune is using or base on JanusGraph or totally build from scratch? Trying to build case to use JanusGraph rather than come up with your own Graph stack in my work. Thanks, - Henry toggle quoted message Show quoted text On Fri, Dec 8, 2017 at 11:23 AM, <mcha...@...> wrote: Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures. They are "essentially" unlimited in the amount of data, or cluster size. Neptune - as of today - is limited to 64TB of data. it has one write master (limiting write capacity) and up to 15 read replicas (liming read capacity). they project that means 100B relations in graph DB - subject to size and number of string properties On Friday, December 8, 2017 at 12:20:23 PM UTC-5, Stephen Mallette wrote: That's an interesting statement....could you elaborate? On Fri, Dec 8, 2017 at 11:39 AM, <mc...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/e1e6b984-2fe2-4c47-b0cb-099dd9af2927%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
Ted Wilmes <twi...@...> #562 Hi Henry, I'm not from Amazon, but it looks like it has no relation to JanusGraph. From what I've read, I think it might have some Blazegraph DNA in it: http://www.snee.com/bobdc.blog/2017/12/sparql-and-amazon-web-services.html. --Ted toggle quoted message Show quoted text On Friday, February 9, 2018 at 12:56:45 PM UTC-6, Henry Saputra wrote: Sorry to follow up on old thread, anyone from AWS could chime whether Neptune is using or base on JanusGraph or totally build from scratch? Trying to build case to use JanusGraph rather than come up with your own Graph stack in my work. Thanks, - Henry On Fri, Dec 8, 2017 at 11:23 AM, <mcha...@...> wrote: Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures. They are "essentially" unlimited in the amount of data, or cluster size. Neptune - as of today - is limited to 64TB of data. it has one write master (limiting write capacity) and up to 15 read replicas (liming read capacity). they project that means 100B relations in graph DB - subject to size and number of string properties On Friday, December 8, 2017 at 12:20:23 PM UTC-5, Stephen Mallette wrote: That's an interesting statement....could you elaborate? On Fri, Dec 8, 2017 at 11:39 AM, <mc...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/e1e6b984-2fe2-4c47-b0cb-099dd9af2927%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
Henry Saputra <henry....@...> #563 Hi Ted, Thanks for sharing the link. Interesting given integration with Dynamo for JanusGraph ... But support for RDF/SPARQL could be nice integration for some use cases. - Henry toggle quoted message Show quoted text On Sun, Feb 11, 2018 at 8:02 AM, Ted Wilmes <twi...@...> wrote: Hi Henry, I'm not from Amazon, but it looks like it has no relation to JanusGraph. From what I've read, I think it might have some Blazegraph DNA in it: http://www.snee.com/bobdc.blog/2017/12/sparql-and-amazon-web-services.html. --Ted On Friday, February 9, 2018 at 12:56:45 PM UTC-6, Henry Saputra wrote: Sorry to follow up on old thread, anyone from AWS could chime whether Neptune is using or base on JanusGraph or totally build from scratch? Trying to build case to use JanusGraph rather than come up with your own Graph stack in my work. Thanks, - Henry On Fri, Dec 8, 2017 at 11:23 AM, <mcha...@...> wrote: Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures. They are "essentially" unlimited in the amount of data, or cluster size. Neptune - as of today - is limited to 64TB of data. it has one write master (limiting write capacity) and up to 15 read replicas (liming read capacity). they project that means 100B relations in graph DB - subject to size and number of string properties On Friday, December 8, 2017 at 12:20:23 PM UTC-5, Stephen Mallette wrote: That's an interesting statement....could you elaborate? On Fri, Dec 8, 2017 at 11:39 AM, <mc...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/e1e6b984-2fe2-4c47-b0cb-099dd9af2927%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-dev+unsubscribe@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/2d2ed41e-64f1-4a2d-a204-2991a96e55d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
Alexander Patrikalakis <amcpatr...@...> #569 I just published support for JanusGraph 0.2.0 to Maven today: https://search.maven.org/#artifactdetails%7Ccom.amazonaws%7Cdynamodb-janusgraph-storage-backend%7C1.2.0%7Cjar https://github.com/awslabs/dynamodb-janusgraph-storage-backend/releases/tag/jg0.2.0-1.2.0 I will double up to track 0.3.0 track support over the coming weeks. Thank you Alex toggle quoted message Show quoted text On Sunday, February 11, 2018 at 9:14:26 PM UTC-8, Henry Saputra wrote: Hi Ted, Thanks for sharing the link. Interesting given integration with Dynamo for JanusGraph ... But support for RDF/SPARQL could be nice integration for some use cases. - Henry On Sun, Feb 11, 2018 at 8:02 AM, Ted Wilmes <t...@...> wrote: Hi Henry, I'm not from Amazon, but it looks like it has no relation to JanusGraph. From what I've read, I think it might have some Blazegraph DNA in it: http://www.snee.com/bobdc.blog/2017/12/sparql-and-amazon-web-services.html. --Ted On Friday, February 9, 2018 at 12:56:45 PM UTC-6, Henry Saputra wrote: Sorry to follow up on old thread, anyone from AWS could chime whether Neptune is using or base on JanusGraph or totally build from scratch? Trying to build case to use JanusGraph rather than come up with your own Graph stack in my work. Thanks, - Henry On Fri, Dec 8, 2017 at 11:23 AM, <mc...@...> wrote: Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures. They are "essentially" unlimited in the amount of data, or cluster size. Neptune - as of today - is limited to 64TB of data. it has one write master (limiting write capacity) and up to 15 read replicas (liming read capacity). they project that means 100B relations in graph DB - subject to size and number of string properties On Friday, December 8, 2017 at 12:20:23 PM UTC-5, Stephen Mallette wrote: That's an interesting statement....could you elaborate? On Fri, Dec 8, 2017 at 11:39 AM, <mc...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/e1e6b984-2fe2-4c47-b0cb-099dd9af2927%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/2d2ed41e-64f1-4a2d-a204-2991a96e55d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More
crs...@... #999 Hello Are you intending on creating the adapter for Janusgraph 3.0 / DynamoDB? Thanks Chris toggle quoted message Show quoted text On Thursday, 8 March 2018 20:14:07 UTC, Alexander Patrikalakis wrote: I just published support for JanusGraph 0.2.0 to Maven today: https://search.maven.org/#artifactdetails%7Ccom.amazonaws%7Cdynamodb-janusgraph-storage-backend%7C1.2.0%7Cjar https://github.com/awslabs/dynamodb-janusgraph-storage-backend/releases/tag/jg0.2.0-1.2.0 I will double up to track 0.3.0 track support over the coming weeks. Thank you Alex On Sunday, February 11, 2018 at 9:14:26 PM UTC-8, Henry Saputra wrote: Hi Ted, Thanks for sharing the link. Interesting given integration with Dynamo for JanusGraph ... But support for RDF/SPARQL could be nice integration for some use cases. - Henry On Sun, Feb 11, 2018 at 8:02 AM, Ted Wilmes <t...@...> wrote: Hi Henry, I'm not from Amazon, but it looks like it has no relation to JanusGraph. From what I've read, I think it might have some Blazegraph DNA in it: http://www.snee.com/bobdc.blog/2017/12/sparql-and-amazon-web-services.html. --Ted On Friday, February 9, 2018 at 12:56:45 PM UTC-6, Henry Saputra wrote: Sorry to follow up on old thread, anyone from AWS could chime whether Neptune is using or base on JanusGraph or totally build from scratch? Trying to build case to use JanusGraph rather than come up with your own Graph stack in my work. Thanks, - Henry On Fri, Dec 8, 2017 at 11:23 AM, <mc...@...> wrote: Cassandra and DynamDB have similar eventually consistent, scale-out, cluster types of architectures. They are "essentially" unlimited in the amount of data, or cluster size. Neptune - as of today - is limited to 64TB of data. it has one write master (limiting write capacity) and up to 15 read replicas (liming read capacity). they project that means 100B relations in graph DB - subject to size and number of string properties On Friday, December 8, 2017 at 12:20:23 PM UTC-5, Stephen Mallette wrote: That's an interesting statement....could you elaborate? On Fri, Dec 8, 2017 at 11:39 AM, <mc...@...> wrote: I'm sure that is part of it. However Neptune does not scale out like DynamDB does. For some people, Neptune will not work. On Thursday, December 7, 2017 at 1:59:47 PM UTC-5, Robert Dale wrote: It probably has to do with the fact that Amazon recently announced their own graph technology - https://aws.amazon.com/neptune/ Robert Dale On Thu, Dec 7, 2017 at 1:16 PM, <mc...@...> wrote: In conversations with AWS, they've expressed little willingness to continue to support this backend. I am very interested in moving from a self-managed cassandra-on-aws graph, to a managed DynamoDB graph. My company has expressed misgivings about basing our solution on an unsupported code base. Is it possible that AWS could be persuaded to contribute the code to JanusGraph, and that JanusGraph would be willing to maintain it going forward? what is needed to make that happen? -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/bc9e62d1-536b-4d1a-bfda-920434d07c9c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b1e95aa2-e153-493d-ace8-2dfebbc64167%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/e1e6b984-2fe2-4c47-b0cb-099dd9af2927%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "JanusGraph developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/2d2ed41e-64f1-4a2d-a204-2991a96e55d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
More

1 - 10 of 10

Previous Topic Next Topic

Home Hashtags Subgroups Calendar Terms