Hello, I would like to announce the second online JanusGraph community meetup. We have a great lineup of sessions that will be given by JanusGraph community members and lots of time for interactive

Hi, I am running SparkGraphComputer for ShortestPathVertexProgram and I am running into Out Of Memory issue with bigger clusters as well. Total Nodes: 10 Million Total Size Of Nodes: 10G approx Total

[ moving discussion from *-users@ to *-dev@ group ] FYI, since future users who are not already subscribed to the mailing list will most likely find this release via GitHub release page and not from

This vote is now closed with a total of 6 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (3 -- Florian Hockmann, Ted Wilmes, Misha Brukman) 0 (0) -1 (0) NON-BINDING VOTES: +1 (3 --

Checked signature, skimmed the docs and sanity-checked binaries. VOTE: +1

Release looks good to me. JanusGraph 0.4 is running as readonly instance for some time without any problem. VOTE: +1 Thanks, Jan

+1 I'd really like to see all of our current known github vulnerabilities get addressed in 0.5.0 as well. Also we should add a graph of the gods with schema constraints to improve testing and user

VOTE: +1

Release looks good. I verified signatures, skimmed through the docs, extracted the zip, tried out some of the new features listed in the change log (lots of good stuff in here!) and then ran a set of

Downloaded release artifacts. - Check the key exists in KEYS file: Done - Verify janusgraph-0.4.0-hadoop2.zip and janusgraph-0.4.0-hadoop2-doc.zip with asc keys: Done - Extract janusgraph-0.4.0.zip,

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

I also think that we need some policy but it is hard to say right now where should this "enhancement" go. Some improvements cannot go to older branches and some can. For example, it could be a storage

Hello, I didn't research much, but I think we could try to enable some platform which will work to collect money contributions which we can spent on some expenses. I didn't research much how it works

+1 If there are folks in the community that want continued support for old/non-supported versions of backend dependencies, we would need those same folks to step up to help managing those maintenance

I'm fine with adding labels for features and breaking changes, but where I'm not sure about is this part: Who decides here which branch to target? The contributor? Any reviewer? I think we should have

Ah, fair enough, enhancement makes sense when explained more fully by example.

I would also add dropping of Cassandra 2 support (including Thrift). These feature set sounds good for me to be integrate into JanusGraph 0.5. The update of TinkerPop 3.4.2 could be integrate also

Hi everyone, 0.2.3 and 0.3.2 are released and 0.4.0 is going to be released soon. I would like to add a new feature "Add support for ElasticSearch 7". The feature makes a small breaking changes, that

If an issue suggests a performance improvement, can we label it as a "bugfix"?

I think "enhancement" can be easily confused with "feature". I'd suggest to stick with "bugfix" for items that would go into any branch.