[ 
https://issues.apache.org/jira/browse/TINKERPOP-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361096#comment-15361096
 ] 

ASF GitHub Bot commented on TINKERPOP-1355:
-------------------------------------------

GitHub user BrynCooke opened a pull request:

    https://github.com/apache/tinkerpop/pull/355

    TINKERPOP-1355 Design HasContainer for extension

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/BrynCooke/incubator-tinkerpop TINKERPOP-1355

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tinkerpop/pull/355.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #355
    
----
commit ca8a4f9fb8a9bc1d69aa10870d75076b8fa906b5
Author: Bryn Cooke <[email protected]>
Date:   2016-07-04T08:29:40Z

    TINKERPOP-1355 Design HasContainer for extension

----


> 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)

Reply via email to