[
https://issues.apache.org/jira/browse/TINKERPOP3-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14534555#comment-14534555
]
Bryn Cooke commented on TINKERPOP3-674:
---------------------------------------
Can't the traversal steps be examined and checked for ids and elements?
The strategy below does this for graph steps, and could be extended for has
steps:
https://github.com/thinkaurelius/titan/blob/0666c46315bfd09778b2282967a3d6c9c0dd890c/titan-core/src/main/java/com/thinkaurelius/titan/graphdb/tinkerpop/optimize/TitanIdsValidationStrategy.java
> Strategy to validate elements or ids
> ------------------------------------
>
> Key: TINKERPOP3-674
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-674
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Bryn Cooke
>
> There are several suite tests that require gremlin queries to be rejected if
> values in a graph step or has step are not all IDs or all elements.
> This feels like something that can be validated at the tinkerpop level via a
> strategy rather then requiring every graph vendor to validate this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
