[
https://issues.apache.org/jira/browse/TINKERPOP-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938811#comment-16938811
]
ASF GitHub Bot commented on TINKERPOP-2280:
-------------------------------------------
spmallette commented on pull request #1195: TINKERPOP-2280 Add
ReservedKeysVerificationStrategy
URL: https://github.com/apache/tinkerpop/pull/1195
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Prevent use of T values as property key overloads
> -------------------------------------------------
>
> Key: TINKERPOP-2280
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2280
> Project: TinkerPop
> Issue Type: Improvement
> Components: structure
> Affects Versions: 3.3.8
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
>
> It's not a great practice but we often see folks overloading "label" and "id"
> as property keys on elements. The problem here is that `valueMap()` will tend
> to end up looking like this:
> {code}
> gremlin> g.V().has('label').valueMap(true)
> ==>[id:13,label:[thing],label:person]
> {code}
> There was an idea to alter the {{toString()}} representation of {{T}} values
> but that didn't seem right after it was done and it's hard to say what
> implications that would have to users. Who knows how {{T}} was used at this
> point.
> [~dkuppitz] suggested that this issue was akin to
> {{EdgeLabelVerificationStrategy}} which is a much less intrusive way to deal
> with the problem, especially going back to 3.3.x. For 3.5.0 we could even
> install this strategy by default as we expected to do with
> {{EdgeLabelVerificationStrategy}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
