[
https://issues.apache.org/jira/browse/TINKERPOP-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757670#comment-17757670
]
ASF GitHub Bot commented on TINKERPOP-2972:
-------------------------------------------
rdtr opened a new pull request, #2216:
URL: https://github.com/apache/tinkerpop/pull/2216
Having duplicate keys does not make sense and a user won't use this feature
(correct me otherwise). But due to the round-robin nature, determining which
traversal should be mapped to the key is complicated in terms of implementation.
So we should throw fast so that we don't have to deal with duplicate keys.
> ProjectStep will produce an unexpected output when dealing with duplicate keys
> ------------------------------------------------------------------------------
>
> Key: TINKERPOP-2972
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2972
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.6.4
> Reporter: Jianzhong Liu
> Priority: Major
>
> g.V().project("a", "b", "b").by("lang").by(T.id).by("age")
> TP:
> 1 \{'b': 29}
> 2 \{'b': 27}
> 3 \{'a': 'java', 'b': '3'}
> 4 \{'b': 32}
> 5 \{'a': 'java', 'b': '5'}
> 6 \{'b': 35}
> TinkerPop erroneously generates an output from the final 'productive'
> by-traversal when a key is used more than once, a situation that should not
> occur. A proposed solution is to throw an exception when a redundant key is
> detected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
