[
https://issues.apache.org/jira/browse/TINKERPOP-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361141#comment-15361141
]
ASF GitHub Bot commented on TINKERPOP-1355:
-------------------------------------------
Github user dkuppitz commented on the issue:
https://github.com/apache/tinkerpop/pull/355
I just implemented my proposed changes. Now we no longer get exceptions,
but unexpected results:
```
gremlin> g.V().hasId(within(new ArrayList()))
==>v[1]
==>v[2]
==>v[3]
==>v[4]
==>v[5]
==>v[6]
gremlin> g.V().hasId(without(new ArrayList()))
==>v[1]
==>v[2]
==>v[3]
==>v[4]
==>v[5]
==>v[6]
```
This should probably go into a separate ticket.
> Design HasContainer for extension
> ---------------------------------
>
> Key: TINKERPOP-1355
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1355
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.0-incubating
> Reporter: Bryn Cooke
> Priority: Critical
>
> Currently HasContainer is final. This means that Graph implementations cannot
> support their own type systems across the entire traversal.
> Given the traversal:
> g.V.has('foo', nonTinkerpopType).out('bar').has('foo', nonTinkerpopType)
> Say that the initial traversal g.V.has('foo', nonTinkerpopType) is dealt with
> via strategy, the non-Tinkerpop type can be dealt with. However the rest of
> the traversal is processed via the default Tinkerpop pipeline, and as such it
> doesn't know how to deal with type conversions/comparisons etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
