Dear developers, I re-corrected the syntax and ran new experiments, still triggered the bugs. ### Expected behavior: We construct the following scenario: we randomly generate two queries Q1, Q2, and

Actually while trying to add more env variables to the janusgraph.env file (posted earlier). I realized that my docker compose of latest Janusgraph (janusgraph/janusgraph:1.0.0-rc2), cassandra:4.1

Thank you Florian. Will try and report back! Yingjie

1) I assume you mean the ConfigurationManagementGraph. You can enable that by setting this env var: gremlinserver.graphs.ConfigurationManagementGraph="/etc/opt/janusgraph/janusgraph.properties"

Would prefer to using existing docker if I could somehow achieve the above with ENV settting etc, if not , could anybody point me to the exact process that I can use to build the docker image from

I was able to create a docker-compose that starts four containers Janusgraph 1.0.0-rc2, Cassandra and OpenSearch based on a repo https://gist.github.com/Phate334/9fd90ddce0eaea74086c1a2e5d419402

Hi Joye, Here you go, in the gremlin console with janusgraph-0.6.3: ``` gremlin> graph =

I guess if I can start the janusgraph 1.0.0-rc2 docker with the configuration that alignes with my customization (excluding the removing extention/jar parts, intially I have to do it due to hgh CVE

I am unfamiliar with packaging so I will wait to see if other experts can chime in. My two cents: you can look at https://github.com/JanusGraph/janusgraph-docker/blob/master/docker-compose-cql-es.yml

Hello Boxuan. Thanks for the pointers. Will it allow me to run with certain configuration, such as use ConfiguredGraphFactory instead of JanusgraphFactory etc? To add a little bit of context

Hi Yingjie, janusgraph/janusgraph:1.0.0-rc2 should be available. You can find it here:

Hello, It appears that the latest janusgraph docker is 0.6.3, and I will need to create a customized docker for Janusgraph 1.0.0.rc2. Any pointers of the steps I should take? Thank you. Yingjie

Hello Marc, Thanks for the pointers, Will try the janusgraph-1.0.0-rc2 with open search 2.6.0 docker. Thanks, Yingjie

Version: 0.6.3 OS: Linux Similar to an issue in OrientDB https://github.com/orientechnologies/orientdb/issues/9933 Here is a simpler case to reproduce: g.addV("v1") g.V().order().by("name") =>

Hi Yingjie Li, The latest janusgraph-1.0.0-rc2 ships with elasticsearch-rest-client 8.6. According to the OpenSearch docs, the latest opensearch versions should be compatible with that. What goes

See https://issues.apache.org/jira/browse/TINKERPOP-2898 Stephen Mallette remarks that in Case 1 and Case 2 the root cause is "in" being a keyword in Groovy. So, implicit anonymous traversals

Please also mention: https://issues.apache.org/jira/browse/TINKERPOP-2897 https://issues.apache.org/jira/browse/TINKERPOP-2895

Hello, Due to the change of ElasticSearch license after 7.10, I need to switch to Open Search for my backend indexing. Any supporting documents on how to set it up? I've been uisng Janusgraph all

OK, received with thanks! I'll start an issue combined with this one: https://lists.lfaidata.foundation/g/janusgraph-users/topic/bug_syntax_error_using/97516169.

I can confirm this one too. Maybe you can combine this issue with the one in https://lists.lfaidata.foundation/g/janusgraph-users/topic/bug_syntax_error_using/97516263 as they might well be