Thanks for the responses Chris and Florian. I'm in agreement that we should first discuss the separate repo issue separate from the implementation details. That was my intent, but by including those

Hi, first of all, big thanks for bringing this up again! I'm really looking forward to an official JanusGraph image. I can think of one advantage of including the Docker images in the main JanusGraph

Hello,I'm regularly using containers for Cassandra and Elasticsearch for my JanusGraph work and I had a couple of thoughts on this. In pull 700 only janusgraph is being run, in the experoinc repo

Hello, I wanted to restart a discussion on producing an official JanusGraph Docker image. There is lots of community interest and progress has been made but we're not quite there yet. There is an

Committers, we're still waiting on approval on the outstanding documentation PR. If you have some time, please review it. There is one new issue regarding a failing CQL test case that needs to get

My opinion is that commented out code can and should be removed. We have the full history in git, and people can find those commented out code blocks in the previous branches 0.1 and 0.2 also. If

Hello. Is there an established convention how no longer useful code should be handled? E.g. there are commented out lines in GraphDatabaseConfiguration.java - like the ones for cluster.partition

Thanks a lot, Jason! I only remembered that there were release candidates for the 0.1.0 release, but I guess that was a special case being the very first JanusGraph release. Anyway, next time we'll

Thanks for the suggestion, Florian. I don't think we published release candidates in the past, instead encouraged developers to build the release from source code. Getting more feedback on the 0.3.0

TinkerPop 3.2.9 was merged on the 0.2 branch last week. There's one documentation PR left outstanding. Once that's merged, I think we're ready to finalize 0.2.1.

Tinkerpop 3.2.9 has been released https://lists.apache.org/thread.html/25804d823e19020d44dc9d353fb1e10b6f811e3b4667e8b0a441c924@%3Cdev.tinkerpop.apache.org%3E

Would it be possible (without requiring too much effort) to publish a release candidate of 0.3.0? Then we could deploy that in our staging environment and give feedback, especially for the new strict

Since there were no objections to adding client drivers to JanusGraph, I went ahead and created a ticket for the .NET part: https://github.com/JanusGraph/janusgraph/issues/1059 Am Freitag, 27. April

Sounds like a good plan, Jason. Thanks for the effort!

Things are shaping up on the Release v0.3.0 milestone. Committers, if you have a time to review/approve some of these outstanding PRs, that would be fantastic. There are also a couple other PRs that

Hi Gene, Have you created the NiFi connector for janusgraph? Thanks, Pawan

Hello Thomas, thank you for your informative response. I was not aware of the existence of Index templates in ES at all. I was thinking of working around the situation by simply changing the Indices

Waiting makes sense to me. Going down the list of open issues, nothing is jumping out to me as critical enough to block going forward the with the release process post 3.2.9 upgrade. --Ted

Very cool, Ted. I'll give it a tire kick.

I'm +1 for JanusGraph housing the client drivers, so users at least wouldn't need to hunt all over for them (unlike storage backends).