Incremental schema changes - Property Key constraint does not exist
Hi All, in our use-case the graph schema is changing over time and we have issues to incrementally add properties to the schema as we get error in the below scenario:
1. day 1: we create a graph with an initial schema: person node with
2. day 2: we try adding
3. day 3: we try adding
We use JanusGraph 1.0.0 with Cassandra 4.0.11 backend.
Below are some snippets to reproduce the above. Could you please have a look and tell us what we are doing wrong?
Day 1 - create initial schema in Gremlin console with session mode - see day1.groovy enclosed
Day 2 - adding lastName property to the person node in Gremlin console with session mode - sew day2.groovy
At this point, once we connect to the graph database,
Day 3 - adding fullName property to the person node in Gremlin console with session mode - see day3.groovy
At this point, once we connect to the graph database,
We have checked with
We have noticed that if we stop and restart JanusGraph, the
Thank you.
1. day 1: we create a graph with an initial schema: person node with
firstName2. day 2: we try adding
lastName3. day 3: we try adding
fullNamegp_traversal.addV('person').property('fullName', 'test full name')Property Key constraint does not exist for given Vertex Label [person] and property key [fullName].We use JanusGraph 1.0.0 with Cassandra 4.0.11 backend.
Below are some snippets to reproduce the above. Could you please have a look and tell us what we are doing wrong?
Day 1 - create initial schema in Gremlin console with session mode - see day1.groovy enclosed
Day 2 - adding lastName property to the person node in Gremlin console with session mode - sew day2.groovy
At this point, once we connect to the graph database,
gp_traversal.addV('person').property('lastName', 'test last name')Day 3 - adding fullName property to the person node in Gremlin console with session mode - see day3.groovy
At this point, once we connect to the graph database,
gp_traversal.addV('person').property('fullName', 'test full name')Property Key constraint does not exist for given Vertex Label [person] and property key [fullName].We have checked with
printSchema()gp_traversal.addV().property('fullName', 'test full name')mgmt.getVertexLabel('person').mappedProperties()fullNameWe have noticed that if we stop and restart JanusGraph, the
fullNameThank you.
Solution
Hello,
you need to close graph in order to take into account new schema constraint, no need to restart server.
You can close graph with ConfiguredGraphFactory.close, then it will automatically open again with GremlinExecutorGraphBinder in JanusGraphManager.
you need to close graph in order to take into account new schema constraint, no need to restart server.
You can close graph with ConfiguredGraphFactory.close, then it will automatically open again with GremlinExecutorGraphBinder in JanusGraphManager.
