https://issues.apache.org/jira/browse/TINKERPOP-2159
Fixed multi-valued property handling in `EventStrategy` / `AddPropertyStep`. The `EventStrategy` output for the traversals added in `TinkerGraphPlayTest.testPlayDK()` is as follows: ``` Vertex [v[1]] added to graph [tinkergraph[vertices:1 edges:0]] Vertex [v[1]] property [vp[name->null]] change to [name1] in graph [tinkergraph[vertices:1 edges:0]] Vertex [v[1]] property [vp[name->name1]] change to [name2] in graph [tinkergraph[vertices:1 edges:0]] Vertex [v[1]] property [vp[name->name2]] change to [name2] in graph [tinkergraph[vertices:1 edges:0]] Vertex [v[2]] added to graph [tinkergraph[vertices:2 edges:0]] Vertex [v[2]] property [vp[name->null]] change to [name1] in graph [tinkergraph[vertices:2 edges:0]] Vertex [v[2]] property [vp[name->null]] change to [name2] in graph [tinkergraph[vertices:2 edges:0]] Vertex [v[2]] property [vp[name->null]] change to [name2] in graph [tinkergraph[vertices:2 edges:0]] Vertex [v[3]] added to graph [tinkergraph[vertices:3 edges:0]] Vertex [v[3]] property [vp[name->null]] change to [name1] in graph [tinkergraph[vertices:3 edges:0]] Vertex [v[3]] property [vp[name->null]] change to [name2] in graph [tinkergraph[vertices:3 edges:0]] Vertex [v[3]] property [vp[name->name2]] change to [name2] in graph [tinkergraph[vertices:3 edges:0]] ``` It's not quite right as the old property will always be `vp[name->null]` when `Cardinality.list` is used or when `Cardinality.set` is used and the value doesn't exist yet. However, I think that's the only to make it work without any major breaking changes. [ Full content available at: https://github.com/apache/tinkerpop/pull/1064 ] This message was relayed via gitbox.apache.org for [email protected]
