Elasticsearch 8 is of course a good point. But do we need to support that directly in 1.0.0? Elasticsearch 7.17 seems to be still supported roughly until 9.0.0 gets released if I understood their EoL

Hi, Upgrade to ElasticSearch 8 will be a breaking change in regarding to Geoshape properties because we won't have Prefix Tree indexing strategy anymore. Users will need to do migration of any indexes

Yes, a release candidate probably makes sense for the 1.0.0 release. I think we don’t need a formal voting process for a release candidate. So, if there are no objections, I start preparing such a

That sounds really awesome! Just one thought: Shall we do a RC release (e.g. 1.0.0 RC1) before the official 1.0.0 release? There are quite some breaking and major changes in 1.0.0, and I feel we

Hi Dustin, sure, that will be included. I should have mentioned that probably: 0.6.3 will include all issues / PRs tagged with the 0.6.3

Hi Florian, Would this release contain the commits in this PR - https://github.com/JanusGraph/janusgraph/pull/2904? v/r Dustin

Hi, I would like to start a discussion about our next release(s) as there were multiple requests from the community already. Our last release (0.6.2) was also already half a year ago (May 31) and

Thanks for starting this thread! Just want to mention there is an open PR for Redis cache integration: https://github.com/JanusGraph/janusgraph/pull/3100

Hello, I would like to start a topic about JanusGraph db-cache we have today and ways to improve it for distributed environments. I want to split this topic on several issues I see with this cache: 1)

Hi Team, Here are the results from the August 2022 license scan of the JanusGraph project. The scan was performed using the Linux Foundation Fossology server. Licenses and copyrights were

Thanks for the clarifications. Kalpa

1. Sure, see: https://github.com/JanusGraph/janusgraph/blob/master/LICENSE.txt 2. JanusGraph backends are not columnar in the usual meaning of the word, but rather assume a BigTable like

Hi All, My company has a inhouse db like elasticsearch but only index based search, no columnar. I see that janusgraph mostly has columnar db as the primary data storage. 1. can we plugin our own

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

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

Thanks for your feedback, Oleksandr. We now have 3 people here on the dev list in favour of starting a Discord Server and no one against it. Only one user responded on janusgraph-users in the

My vote is +1 I must merge the v0.6 branch into master to update the changelog.md. Greetings, Jan

Related thread in Users group: https://lists.lfaidata.foundation/g/janusgraph-users/topic/discuss_moving_from_gitter/91181812

It looks like Discord stores unlimited amount of history like Gitter but it has more features. It's definitely a downside that you need to be registered in Discord for read-only purposes and your

Thank you Florian for taking care of this release. I downloaded JanusGraph Full artifacts, started JanusGraph Server with Cassandra and ElasticSearch, checked that queries from `Basic Usage`