I just tried both zip archives, following our docs on local installation that simply starts JanusGraph Server with ./bin/gremlin-server.sh start. This fails silently which can be noticed when one

+1 for this. Besides Gitter, we should think also about Slack or Discord. Slack is much more common in the industry than Gitter. Discord had gain speed in the open-source communities in the last

I think it's a good idea to have a separate room for each topic as long as it affects enough people to justify having it's own room. So maybe we can start with this one and add more on the fly when

Thanks, Dmitry Let me get to work on this and post back when it's ready -- Ashwin

Hi Ashwin, Thank you for the offering. I think it would be great if you could open source it in your own repo on github, and post links here and in users group. Also if you could share some more info

+1 for this. I have always wanted a Developer's chat room, so that a quick informal question can be asked and be replied faster. Maybe even Slack will do like we have for ScyllaDB. Such way that, if

Hi, we currently have a public chat on Gitter for JanusGraph that is mainly used for questions by users. I think it would be helpful to have another room to discuss about the development of

I'm seeing the same issues with travis-ci.org. If you use travis-ci.com, you also get support actions (tab in a pr). Vote +1

Hi, During an index creation in ES serve , there is a default type is getting added to “mappings” by defaultduring index creation . Later when the application initiates a“PUT” rest method

Hi, We needed an embeddable backing store for Janus on one of our products. Since the Berkley JE license is restrictive , we ended up writing a quick implementation on top of MV

Hi, I have tested the truncated binary distribution, using the a pre-built docker image of janusgraph. My vote is +1. Greetings, Jan

Hi, I have tested the truncated binary distribution. My vote is +1 Regards, Nicolas

Hello, We are happy to announce that JanusGraph 0.5.1 is ready for release. The release artifacts can be found at this location: https://github.com/JanusGraph/janusgraph/releases/tag/v0.5.1 A

Currently we are using travis-ci.org and I often notice periodic problems with that. Sometimes workers stop to process any computation, sometimes website doesn't work (on maintenance), sometimes

This vote is now closed with a total of 4 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (3 -- Oleksandr Porunov, Jan Jansen, Ted Wilmes) 0 (0) -1 (0) NON-BINDING VOTES: +1 (1 --

Vote +1

Vote +1

Hi, As noted in the Janus docs: https://docs.janusgraph.org/advanced-topics/eventual-consistency/ "In order to avoid that write failures result in permanentinconsistencies in the graph it is

Thank you Jan. Yes, I think we can release 0.5.1 as a truncated version short after 0.5.0 release.

I am OK with it. I would prefer to work on truncated short after this release and release 0.5.1 also as truncated release. If opened two PRs for the docker images which are required for releasing