Hi, In case you haven’t seen it already: TinkerPop now has a Discord server, and that Discord has its own channel for implementers which of course includes graph databases like JanusGraph. I

The JanusGraph Technical Steering Committee is excited to announce the release of JanusGraph 0.6.0. JanusGraph is an Apache TinkerPop enabled property graph database with support for a variety of

This vote is now closed with a total of 5 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (3 -- Oleksandr Porunov, Boxuan Li, Florian Hockmann) 0 (0) -1 (0) NON-BINDING VOTES: +1

Thanks for fixing this! I performed the same tests again and now everything looks good. So: VOTE +1 Von: janusgraph-dev@... <janusgraph-dev@...> Im Auftrag von Oleksandr Porunov Gesendet:

I re-uploaded a new staring release. I checked and successfully closed the staging release (1035). GitHub tag v0.6.0 has been updated to point on the latest commit. All the GitHub artifacts has been

Opened a PR here which fixes the issue with `janusgraph.sh`: https://github.com/JanusGraph/janusgraph/pull/2781

Confirming the issue which is found by Florian Hockmann. I was trying to load `GraphOfTheGodsFactory.load(graph)` and couldn't: GraphOfTheGodsFactory.load(graph) The indexing backend with name

I just did a quick test of the two distribution archives which just consists of starting JanusGraph Server and connecting to it via the remote console to create a vertex. For the full distribution, I

I did the following tests: Connected to AWS keyspace, did some simple traversals Compatibility test: using 0.5.3 CQL + ES to create a graph with 10 million nodes

I also executed all TinkerPop tests again with `mvn clean install -Dtest.skip.tp=false -DskipTests=true`. All tests passed.

I realized that I was building with Java 11 instead of Java 8. I switched to the Java 8 (OpenJDK 1.8.0_302), dropped previous staging repository, rebuilt JanusGraph using Java 8, re-uploaded new

Thank you Boxuan! Confirm this issue. Most likely I made a mistake during the build process because I can reproduce this issue with my build but can't reproduce this issue with the next build

I downloaded janusgraph-0.6.0.zip and got this error when using the gremlin console:

I dropped previous staging release from Sonatype account and reuploaded a new staring release. I checked and successfully closed the staging release. GitHub tag v0.6.0 has been updated to point on the

Hi Jan, Thanks for pointing on that! That indeed uploads distribution for a commit but it doesn't provide you with the maven nexus repository to use those distributions. Basically, it means, that you

Hi Porunov We already build release package for any master commit and this release package can be download by anyone. Disclaimer: It doesn't follow our default release guildlines, it just builds it

Hi @vinay1331, This is expected. You must upgrade your Gremlin Server client first. See upgrade instructions regarding your issue here:

After the upgrade to testing getting following exception using remote traversal. Used tinkerpop 3.5.1 with janusgrah drive-0.6.0 WARN

I would like to propose to make simple GitHub jar releases on each commit in `master` or `v*` branches. Those releases would be simple GitHub packages and their purpose wouldn't be mostly for easier

Hi thanks for the quick responses. Followed by Clement’s advice, I made a fix https://github.com/li-boxuan/janusgraph/commit/aec47d44e6b0a57eac5fb5acab4c11d365d0ecac that worked on my local laptop.