J

JanusGraph•11mo ago

pm_osc

Gremlin console ConfiguredGraphFactory issue with 1.1.0 (working fine on 1.0.0)

Also asked here: https://lists.lfaidata.foundation/g/janusgraph-users/topic/gremlin_console/111118784

Hi All,

I am running JanusGraph in container with ConfiguredGraphFactory configured. After upgrading to 1.1.0, ConfiguredGraphFactory.getGraphNames() does not work any more when Gremlin console is used from the container.

On JanusGraph 1.0.0, the below steps work fine:

1. docker run -d -p 8182:8182 --name janusgraph-1.0.0 -e gremlinserver.graphManager=org.janusgraph.graphdb.management.JanusGraphManager -e gremlinserver.graphs.ConfigurationManagementGraph=conf/janusgraph-inmemory-server.properties janusgraph/janusgraph:1.0.0
2. docker exec -it janusgraph-1.0.0 /bin/bash
3. /opt/janusgraph/bin/gremlin.sh
4. :remote connect tinkerpop.server conf/remote.yaml session
5. :remote console
6. ConfiguredGraphFactory.getGraphNames() - I get an empty list which is expectedOn JanusGraph 1.1.0, after executing the below steps 'org.janusgraph.graphdb.management.utils.ConfigurationManagementGraphNotEnabledException: Please add a key named "ConfigurationManagementGraph" to the "graphs" property in your YAML file and restart the server to be able to use the functionality of the ConfigurationManagementGraph class.' error happens:
7. docker run -d -p 8182:8182 --name janusgraph-1.1.0 -e gremlinserver.graphManager=org.janusgraph.graphdb.management.JanusGraphManager -e gremlinserver.graphs.ConfigurationManagementGraph=conf/janusgraph-inmemory-server.properties janusgraph/janusgraph:1.1.0
8. docker exec -it janusgraph-1.1.0 /bin/bash
9. /opt/janusgraph/bin/gremlin.sh
10. :remote connect tinkerpop.server conf/remote.yaml session
11. :remote console
12. ConfiguredGraphFactory.getGraphNames()

Could you please advise if this behaviour on 1.1.0 is intended or a bug?
(I can reproduce the same with Cassandra backend it was just easier to use inMemory while providing repro steps)

Thank you.

Gremlin console ConfiguredGraphFactory issue with 1.1.0 (working fi...

Solution

Thanks @Clément de Groc and @Wleong for the response. For now, we can live with using

:> ConfiguredGraphFactory.getGraphNames()

:> ConfiguredGraphFactory.getGraphNames()

. Thanks for the hints.

Jump to solution