Multiple labels not working in mergeV() syntax for conditional inserts in AWS Neptune
I know that multiple labels are an AWS Neptune specific feature and TinkerPop model does not allow for multiple labels, but maybe someone else has encountered the same problem.
While attempting to migrate conditional inserts (upserts) to the new mergeV/E() syntax, I encountered an issue with vertices that have multiple labels. It appears that creating a vertex with multiple labels only works with the addV() step, which was present in the fold()/coalesce()/unfold() pattern for conditional inserts. In the new syntax, the label property is specified in a map, and a string such as 'Label1::Label2::Label3' will be treated as a single label.
For example, the following code written in Gremlin-Java, creates a vertex with a single label called 'Label1::Label2', instead of 2 separate labels:
Are there any alternative approaches to this issue that make use of the new syntax for efficient upserts?
While attempting to migrate conditional inserts (upserts) to the new mergeV/E() syntax, I encountered an issue with vertices that have multiple labels. It appears that creating a vertex with multiple labels only works with the addV() step, which was present in the fold()/coalesce()/unfold() pattern for conditional inserts. In the new syntax, the label property is specified in a map, and a string such as 'Label1::Label2::Label3' will be treated as a single label.
For example, the following code written in Gremlin-Java, creates a vertex with a single label called 'Label1::Label2', instead of 2 separate labels:
Are there any alternative approaches to this issue that make use of the new syntax for efficient upserts?
Apache TinkerPop is an open source graph computing framework and the home of the Gremlin graph query language.
1,376Members
Resources
Similar Threads
Was this page helpful?
