[
https://issues.apache.org/jira/browse/TINKERPOP-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15796076#comment-15796076
]
Paul Jackson commented on TINKERPOP-920:
----------------------------------------
Neo4j, at least when going through the embedded API, will even let one node
have a property be, say, a single String and another node have, say, an array
of Long for the same key. Perhaps {{Cardinality}} should have an additional
value such as {{undefined}}? Feel free to ignore my comment if it's off topic
:).
> Test case needed for ensuring same cardinality for key.
> -------------------------------------------------------
>
> Key: TINKERPOP-920
> URL: https://issues.apache.org/jira/browse/TINKERPOP-920
> Project: TinkerPop
> Issue Type: Improvement
> Components: test-suite
> Affects Versions: 3.0.2-incubating
> Reporter: Marko A. Rodriguez
> Assignee: stephen mallette
> Labels: breaking
>
> I'm note sure we have a test case for this so I will just make a ticket --
> please close with "won't fix" if this is already handled.
> Two properties with the same key should NOT have different cardinalities
> because of {{Feature.getCardinality(key)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
