vertex-label-with-given-name-does-not-existERROR with Janusgraph 0.5.3
vertex-label-with-given-name-does-not-exist
ERROR with Janusgraph 0.5.3 while adding labels to vertices
I get this error only when I enable storage.batch-loading=true.
My schema.default is still set to default when checking from gremlin console. mgmt.get("schema.default") => default
My understanding is schema default should allow us to add undefined labels, properties etc
Has anyone faced this ?
ERROR with Janusgraph 0.5.3 while adding labels to vertices
I get this error only when I enable storage.batch-loading=true.
My schema.default is still set to default when checking from gremlin console. mgmt.get("schema.default") => default
My understanding is schema default should allow us to add undefined labels, properties etc
Has anyone faced this ?
Solution
Any reason why you need automatic schema creation (
This feature is mainly intended for cases where you just want to try out JanusGraph and don't want to bother with creating a schema. But it's not intended for production use cases.
The docs also discourage its usage in general:
and explicitly in combination with
I'd also suggest updating to JanusGraph 1.0.0 in general, but that shouldn't change much about your problem
schema.default=noneThis feature is mainly intended for cases where you just want to try out JanusGraph and don't want to bother with creating a schema. But it's not intended for production use cases.
The docs also discourage its usage in general:
It is strongly encouraged to explicitly define all schema elements and to disable automatic schema creation by setting schema.default=none in the JanusGraph graph configuration.https://docs.janusgraph.org/schema/#automatic-schema-maker
and explicitly in combination with
batch-loadingImportant: Enabling storage.batch-loading requires the user to ensure that the loaded data is internally consistent and consistent with any data already in the graph. In particular, concurrent type creation can lead to severe data integrity issues when batch loading is enabled. Hence, we strongly encourage disabling automatic type creation by setting schema.default = none in the graph configuration.https://docs.janusgraph.org/operations/bulk-loading/
I'd also suggest updating to JanusGraph 1.0.0 in general, but that shouldn't change much about your problem
