Usage of single cardinality AWS Neptune

hey, i've been looking around and haven't been able to find much good documentation on this so figured i'd ask here. i'm trying to doing upsertion via the efficient merge commands for gremlin in AWS Neptune. i've got a couple properties on the edges but it seem that the single cardinality isn't supported with mergeE. specificially, something like options with onCreate and onMatch:
option(onCreate, [(from):'v1', (to):'v2', 'property': single('value')])
option(onCreate, [(from):'v1', (to):'v2', 'property': single('value')])
it's just weird cause it's been working for mergeV is there a different syntax or a different way to do it for mergeE?
Solution:
Edge properties can only be single cardinality. So there's no need to specify cardinality when specifying properties for mergeE. https://tinkerpop.apache.org/docs/3.6.1-SNAPSHOT/reference/#vertex-properties ...
Moreover, while an Edge can only have one property of key "name" (for example), a Vertex can have multiple "name" properties....
Jump to solution
2 Replies
Solution
triggan
triggan2w ago
Edge properties can only be single cardinality. So there's no need to specify cardinality when specifying properties for mergeE. https://tinkerpop.apache.org/docs/3.6.1-SNAPSHOT/reference/#vertex-properties ...
Moreover, while an Edge can only have one property of key "name" (for example), a Vertex can have multiple "name" properties.
JK
JKOP2w ago
ah that makes sense. thanks for the help

Did you find this page helpful?