Janusgraph 1.0.0 Export and Import

[angu2015]

Janusgraph Export and Import using GyroWriter.writeGraph is exporting successfully but while import it throws Missing VertexID. Any other method to export as whole graph in binary form? I am using janusgraph 1.0.0

[li-boxuan]

Could you please provide the full stacktrace?

This may or may not have been fixed by https://github.com/JanusGraph/janusgraph/pull/4278/files. Anyways, it's worth trying the "unreleased" version. If you use JanusGraph as a library we do publish a version for every commit on main.

[angu2015]

I tried the unreleased version it's working now. the export and import of graph using gyro is working as expected. I am not using it as library. I did a unit test by building the master branch and generated the zip and run it as a server. Thanks for helping me.

[angu2015]

The same issue occurred for ConfigurationManagementGraph. Here is the trace of Error log

07:17:45 WARN org.apache.tinkerpop.gremlin.server.op.AbstractEvalOpProcessor.lambda$evalOpInternal$7 - Exception processing a script on request [RequestMessage{, requestId=d9337893-9662-4da7-812e-e7bf70f2e483, op='eval', processor='session', args={gremlin=confMap = new HashMap();confMap.put('storage.backend', 'inmemory');confMap.put('graph.set-vertex-id', 'true');confMap.put('storage.hostname', '127.0.0.1');confMap.put('graph.allow-custom-vid-types', 'true');ConfiguredGraphFactory.createTemplateConfiguration(new MapConfiguration(confMap));, session=timetravel-1720595861683, manageTransaction=false, batchSize=64, maintainStateAfterException=false}}]. java.lang.IllegalArgumentException: Must provide vertex id at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145) ~[guava-33.1.0-jre.jar:?] at org.janusgraph.graphdb.transaction.StandardJanusGraphTx.addVertex(StandardJanusGraphTx.java:632) ~[janusgraph-core-1.1.0-SNAPSHOT.jar:?] at org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsTransaction.addVertex(JanusGraphBlueprintsTransaction.java:138) ~[janusgraph-core-1.1.0-SNAPSHOT.jar:?] at org.janusgraph.graphdb.tinkerpop.JanusGraphBlueprintsGraph.addVertex(JanusGraphBlueprintsGraph.java:143) ~[janusgraph-core-1.1.0-SNAPSHOT.jar:?] at org.janusgraph.graphdb.management.ConfigurationManagementGraph.createTemplateConfiguration(ConfigurationManagementGraph.java:149) ~[janusgraph-core-1.1.0-SNAPSHOT.jar:?] at org.janusgraph.core.ConfiguredGraphFactory.createTemplateConfiguration(ConfiguredGraphFactory.java:243) ~[janusgraph-core-1.1.0-SNAPSHOT.jar:?] at org.codehaus.groovy.vmplugin.v8.IndyInterface.fromCache(IndyInterface.java:321) ~[groovy-4.0.9.jar:4.0.9] at Script6.run(Script6.groovy:1) ~[?:?] at org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:679) ~[gremlin-groovy-3.7.2.jar:3.7.2] at org.apache.tinkerpop.gremlin.groovy.jsr223.GremlinGroovyScriptEngine.eval(GremlinGroovyScriptEngine.java:381) ~[gremlin-groovy-3.7.2.jar:3.7.2] at java.scripting/javax.script.AbstractScriptEngine.eval(AbstractScriptEngine.java:233) ~[java.scripting:?] at org.apache.tinkerpop.gremlin.groovy.engine.GremlinExecutor.lambda$eval$0(GremlinExecutor.java:314) ~[gremlin-groovy-3.7.2.jar:3.7.2] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.base/java.lang.Thread.run(Thread.java:829) [?:?]

[angu2015]

Any update on this. @li-boxuan

[li-boxuan]

ConfigurationManagementGraph is like a meta-graph that stores metadata about each of your real graphs. This meta-graph is internally managed by JanusGraph and must not set graph.set-vertex-id=true or graph.allow-custom-vid-types=true

[angu2015]

Even in that to store the meta data of the graph it should support what the vertex Id used by the real graph and it should not auto generated by the janusgraph. And in another case If I want to load the multiple graph snap shot in to the Janusgraph Server we have to use the ConfigurationManagementGraph right? In that case it has to allow the custom vertex id in order to use the same vertex id present in the snapshot. graph.set-vertex-id=true property is allowed for ConfigurationManagement graph in 0.6.3 or before.

[li-boxuan]

And in another case If I want to load the multiple graph snap shot in to the Janusgraph Server we have to use the ConfigurationManagementGraph right

Yes

In that case it has to allow the custom vertex id in order to use the same vertex id present in the snapshot

No I don't think so. Your ConfigurationManagementGraph: conf/JanusGraph-configurationmanagement.properties settings could be different from normal graphs.

graph.set-vertex-id=true property is allowed for ConfigurationManagement graph in 0.6.3 or before.

Thanks, I wasn't aware of that. I'll investigate why it worked before.

[li-boxuan]

graph.set-vertex-id=true property is allowed for ConfigurationManagement graph in 0.6.3 or before.

@angu2015 are you sure? I reproduced the problem on v0.6 branch.

[angu2015]

@li-boxuan Yes you are right. it's throwing the same error in 0.6 as well. Sorry for the confusion.