All tests that are using JUnitBenchmarkProvider need to be replaced. https://github.com/JanusGraph/janusgraph/search?q=JUnitBenchmarkProvider&unscoped_q=JUnitBenchmarkProvider Am Freitag, 1. Februar

Relevant to this topic: https://github.com/JanusGraph/janusgraph/issues/1395 I see that some benchmark tests are removed in that PR. Should we log them somewhere? I think we can provide links in that

Chris, thanks a lot for this report! Awesome work. I like the blurb for issues closing.

For upgrade of Cassandra, Cassandra support of 2.1 is downgrade to only patch critical things https://cassandra.apache.org/download/. There are currently multipledifferent backend which have support

There were 366 issues initially, 3 of which I already closed. I'm proposing that we can we close out an additional 88 issues shown below. I'll do the actual cleanup early next week. Here's the blurb

Hi everyone, Barring additional reviews I plan to merge the PR to upgrade junit to 5 next Wednesday once it hits lazy consensus. I don't think there's much in the pipeline that would affect it, but

+1 on EOL on 0.2 soon and branch off 0.3 from master. Jerry

I think that it will be too much pain to support more than 2 branches right now. I also think that 0.2.3 release should be the last one in the 0.2 branch and then we can support 0.3 and 0.4 versions.

There are currently two issues that we probably want to include in a release soon: Upgrade to TinkerPop 3.4.0 (#1364) Upgrade Cassandra to 2.2 (#1398) These two issues are too big in my opinion to be

+1 As someone who sometimes forgets to sign his commits I fully support bot checking.

I think we should deprecate Thrift soon and then remove it in the next minor version of JanusGraph after that, but we probably need to offer the same functionality for CQL as for Thrift before we can

This group is meant to discuss development of JanusGraph itself. For usage questions, please use JanusGraph users and for questions about Gremlin in general, like this one, you can use

+1 Good idea! I sometimes close old issues if I come by them for some reason and notice that they aren't really issues (anymore), but going through all issues systematically would be great. Am

+1 for number 3. Number 3 is probably the best option, but I do wonder how long we should continue to support things like thrift and upgrading from titan.

Hi all How can I get the executing query as string?

Hello, The new template for issues got me thinking about going through all of the issues and closing out the ones that belong as user group messages, duplicates, or issues that may have already been

Hello, In the print schema PR, A user asked about returning json instead of a text table. It wouldn't be difficult to return all the data as a String formatted as json and I can just add it in a

Hello, For such kind of questions use this group: https://groups.google.com/forum/#!forum/janusgraph-users I think you should look at OGMs. For example this one: http://syncleus.com/Ferma/ Regards

Hi all, Is there a simple way to map returning vertices or value maps to Java Pojo? Any suggestions? Thanks a lot!

Option 3 balances the various interests without nicely, +1 for it