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

Hi Jan, I think that it isn't a big problem that current release is 2 times bigger than past releases. Of course we can try to ship also truncated releases but it looks more like a new feature. We

Hi Nicolas. This isn't a release specific warning but ES specific. You may find the same warning with JanusGraph 0.3.x, 0.4.x versions.

We could think of adding a smaller release bundle without janusgraph.sh, cassandra and elasticsearch. For the current release, we could try to run elasticsearch with default jdk. It shouldn't be any

Hi, I found how to fix the warning "the default number of shards will change from [5] to [1] in 7.0.0" with the option index.search.elasticsearch.create.ext.number_of_shards documentated at

Hi, I have tested the release using cassandra 3.0.17 and elasticsearch 6.8.6. I have been able to use a graph loaded with janusGraph 0.4.1. I have also created a new graph with about 800 000 vertices

Thank you Ted for the review of the release! Yes, I also noticed that now jdk is included into elasticsearch. This change was made in the next commit:

Thanks for leading this release Oleksandr! I downloaded 0.5.0 and noticed the zip is quite large. It looks like there is a jdk that got bundled under Elasticsearch: 20M

I want to say that the release is targeting the latest commit: https://github.com/JanusGraph/janusgraph/commit/c01bfea2ce602696163aa50fde9be1cdeea13fc1 The release has been tested with following

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