supportsMultiProperties returning true will only enable tests that have that
feature requirement. it won't disable any tests.
shouldTriggerAddVertexViaMergeV is assuming single cardinality here. if it was
multiproperty the cardinality would have had to be explicitly defined as:
gremlin> g.mergeV([any:'thing']).property(list, 'any','thing')
==>v[0]
gremlin> g.V().valueMap()
==>[any:[thing,thing]]
On 2022/10/06 15:49:24 Grant Haywood wrote:
> Hello,
>
> Quick question on the test case "shouldTriggerAddVertexViaMergeV" in
> "org.apache.tinkerpop.gremlin.process.traversal.strategy.decoration.Eve
> ntStrategyProcessTest"
>
> This case remains enabled when supportsMultiProperties returns true.
> The following code appears to assert (for a starting empty graph), if
> merge creates the property ("any", "thing"), then property("any",
> "thing") is called, there should only be 1 property stored.
> m.put("any", "thing");
> gts.V().mergeV(m).property("any", "thing").next();
>
> tryCommit(tinkerGraph, g -> assertEquals(1,
> IteratorUtils.count(gts.V().has("any", "thing"))));
>
> This seems like the correct behavior for Set cardinally, but is this
> test case correct for List cardinally?
>
> Thanks for any clarification you can provide.
>
