Issue with enabling user supplied id in JanusGraph #4660
-
Hello, I am encountering an issue while trying to configure JanusGraph to allow user-supplied-ids. I followed the guide and made the necessary settings, but it seems they are not taking effect. Here are the details of my environment and the steps I have taken: 15:50:12 INFO org.janusgraph.diskstorage.configuration.builder.ReadConfigurationBuilder.setupTimestampProvider - Set default timestamp provider MICRO 15:50:12 INFO org.janusgraph.graphdb.idmanagement.UniqueInstanceIdRetriever.getOrGenerateUniqueInstanceId - Generated unique-instance-id=7f0001012947944-ubuntu1 15:50:12 INFO org.janusgraph.diskstorage.configuration.ExecutorServiceBuilder.buildFixedExecutorService - Initiated fixed thread pool of size 320 15:50:12 INFO org.janusgraph.graphdb.database.StandardJanusGraph. - Gremlin script evaluation is disabled 15:50:12 INFO org.janusgraph.diskstorage.log.kcvs.KCVSLog$MessagePuller.initializeTimepoint - Loaded unidentified ReadMarker start time 2024-08-29T07:50:12.927784Z into org.janusgraph.diskstorage.log.kcvs.KCVSLog$MessagePuller@148fca83 ==>standardjanusgraph[inmemory:[127.0.0.1]] gremlin> mgmt = graph.openManagement() ==>org.janusgraph.graphdb.database.management.ManagementSystem@3a13f663 gremlin> mgmt.set("graph.set-vertex-id", true) ==>org.janusgraph.diskstorage.configuration.UserModifiableConfiguration@56f61d74 gremlin> mgmt.commit() ==>null However, when I called graph.features(), the result indicates that the setting has not been applied. See ==>FEATURES
` I am aware that the setting graph.set-vertex-id is of GLOBAL_OFFLINE mutability level according to the Configuration Reference, so I have not started any traversal instances on the graph, which I believe is the correct approach. Could you please advise what might be causing this issue and how I can resolve it? Thank you for your assistance. Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
What you have observed is expected. You will see
once you enable |
Beta Was this translation helpful? Give feedback.
Oh sorry I read your post too quickly. IIRC in-memory backends don't support changing GLOBAL_OFFLINE configs because you basically need to restart your graph for new configs to take effect. There's no "restart" concept for in-memory graphs since they are not persistent.
You could try to set the values when you start the graph.