[ https://issues.apache.org/jira/browse/TINKERPOP-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17741121#comment-17741121 ]
ASF GitHub Bot commented on TINKERPOP-2957: ------------------------------------------- spmallette opened a new pull request, #2127: URL: https://github.com/apache/tinkerpop/pull/2127 https://issues.apache.org/jira/browse/TINKERPOP-2957 Provides a nicer way to allow users to control cardinality of property values when using mergeV() and property(Map). A bit tough to get this in without changes to the serializers but by treating the CardinalityValue as a special form of Bytecode it allowed this change to keep the serializers sacred. VOTE +1 > mergeV with sideEffect not correctly updating properties > -------------------------------------------------------- > > Key: TINKERPOP-2957 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2957 > Project: TinkerPop > Issue Type: Bug > Components: process > Affects Versions: 3.6.4 > Reporter: Kelvin Lawrence > Assignee: Stephen Mallette > Priority: Blocker > > A Gremlin user let me know about the following issue. If the query below is > run twice, the name parameter on the 4567 vertex does not get updated. The > name on the 1234 vertex does get updated. The query is written this way as > not all databases support single cardinality as the default. The issue has > been reproduced using both TinkerGraph and Amazon Neptune. > {code:java} > g.mergeV([(T.id): 'test-test-1234']). > option(onCreate, [(T.label): 'someLabel', 'name': 'name1']). > option(onMatch, sideEffect(property(single,"name","name2")).constant([:])). > mergeV([(T.id): 'test-test-4567']). > option(onCreate, [(T.label): 'someLabel', 'name': 'name1']). > option(onMatch, > sideEffect(property(single,"name","name2")).constant([:])){code} -- This message was sent by Atlassian Jira (v8.20.10#820010)