There are several existing graph db benchmarking frameworks, e.g., https://github.com/socialsensor/graphdb-benchmarks — supports several graph dbs, including Titan; should be updated to support

That didn't compile. I changed it to use Key: .repeat(_.outE().inV().has(Key[Long]("num"),gt(50)).simplePath()) oddly enough it filters everything although clearly some ages do have higher than 50 in

Does that mean you want to exclude the whole path or only matching vertices on the path? If the latter, then what about the edges? Taking out a single vertex leaves 2 invalid edges on the path. If the

What's the best way to filter a path based on a Vertex property. I am using the gremlin-scala lib. This is the code: val paths = startVertex.asScala().start()

Does anyone know of a good scala client? Shold I use 'gremlin-scala_2.12'?

Hello, Can someone let me know if there is a benchmarking tool for Graph Dbs (particularly for JanusGraph) like YCSB for NOSQL databases and Cassandra-Stress specific tp Cassandra Db. Anyone using

Welcome, David! It's great to have you on board!

Thank you for looking into this for me. In general, Janus seems pretty spiffy. Nice work done here so far.

Thanks for the reproduce scenario. I opened up an issue to track this https://github.com/JanusGraph/janusgraph/issues/487

Congrats and welcome, David!

For the record, the output of the same script when run against TinkerGraph 3.2.6 is as expected: properties: [{'string_prop': [vp[string_prop->dave]], 'integer_prop': [vp[integer_prop->1]],

Ok, I built from source. It appears that this is happening specifically with properties defined as Floats. The following script in gremlin_python (3.2.6) illustrates this problem: from

Would you be able to test your scenario against JanusGraph master branch? It's running TP 3.2.6.

A bit of a follow up on this. I have determined that the source of my problem relates to selecting an individual vertex property from a list cardinality property. I use this traversal:

On Monday, August 28, 2017 at 4:01:40 PM UTC-4, David Brown wrote: Thanks for the quick replies. Thanks to the examples, I've determined this is a bug in Goblin. On Monday, August 28, 2017 at 2:07:38

On behalf of the JanusGraph Technical Steering Committee (TSC), I'm pleased to welcome a new committer on the project! David Clement has submitted several good pull requests which enhanced the

Janus is such a compelling database to switch to. Right now we use Neo4j. There are a couple of features that neo4j has that are very useful and I was wondering if they are on the roadmap for

Thanks for the quick replies. Thanks to the examples, I've determined this is a bug in Goblin.

I opened up an issue to add docs on meta-properties and multi-properties. This worked in the Gremlin Console: gremlin> graph = JanusGraphFactory.build().set('storage.backend',

Hello JanusGraph users, I have been experimenting with Janus, and using the automatic schema generation, metaproperties work as expected. However, when I set `schema.default=none` in the conf and