Well, the way it works now (in this PR) kinda makes sense. The current behavior has not been changed, new code paths were only introduced for the cases that threw exceptions previously:
`Cardinality.list`: Now triggers a change event, with the old property always being empty (makes sense, because the new property will always be added and not change an existing one) `Cardinality.set`: The old property will be empty if the value doesn't exist yet, otherwise, it will be the property with the existing value. Not too bad, IMO. The proper way would be to change `VertexProperty`, so that it combines all values with the same key (e.g. in `The Crew` graph every person would have only one `location` property w/ multiple values), but that really is too much of a breaking change I think. [ Full content available at: https://github.com/apache/tinkerpop/pull/1064 ] This message was relayed via gitbox.apache.org for [email protected]
