[
https://issues.apache.org/jira/browse/TINKERPOP-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606149#comment-15606149
]
stephen mallette edited comment on TINKERPOP-920 at 1/3/17 5:56 PM:
--------------------------------------------------------------------
[~okram] this would be a nice validation except that TinkerGraph/Neo4j
(probably others) don't have a good way to support it because they don't have a
schema. {{Feature.getCardinality(k)}} in both TinkerGraph and Neo4j rely on
configuration to return those values. The cardinality is either always {{list}}
or always {{set}} or always {{single}} for them. With something like Titan you
actually consult a schema so this would probably work better in that case, but
that would still leave us and most providers with how to nicely implement such
a thing.
Any ideas on what to do here? or should we just close this one?
was (Author: spmallette):
[~okram] this would be a nice validation except that TinkerGraph/Neo4j
(probably others) don't have a good way to support it because they don't have a
schema. {{Feature.getCardinality(k)}} in both TinkerGraph and Neo4j rely on
configuration to return those values. The cardinality is either always {{list}}
or always{{set}} or always {{single}} for them. With something like Titan you
actually consult a schema so this would probably work better in that case, but
that would still leave us and most providers with how to nicely implement such
a thing.
Any ideas on what to do here? or should we just close this one?
> 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)
