[
https://issues.apache.org/jira/browse/TINKERPOP-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-920:
---------------------------------------
Labels: (was: breaking)
Component/s: (was: test-suite)
structure
Re-reading comments from where this was last left. I don't think we should
enforce cardinality to a key. Instead {{getCardinality}} should be documented
as a method that provides a cardinality hint that can be used by internal
TinkerPop methods. I'd also rather not make significant changes here because
{{getCardinality}} just takes a String right now. That may be insufficient for
more advanced graph schemas like those that allow a vertex label namespace for
properties such that the key isn't just the property key but is the vertex
label plus the property key. Better to wait for more developments in that space
before committing to a breaking change here.
> 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: structure
> Affects Versions: 3.0.2-incubating
> Reporter: Marko A. Rodriguez
> Assignee: stephen mallette
>
> 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.4.14#64029)
