tinkerpop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TINKERPOP-1355) Design HasContainer for extension
Date Mon, 04 Jul 2016 10:36:10 GMT

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

ASF GitHub Bot commented on TINKERPOP-1355:

Github user BrynCooke commented on the issue:

    Also the conversion of the collection to an array is dangerous. Who knows what the collection
is actually backed by? It should use an iterator and get the first element if it exists.

> 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

This message was sent by Atlassian JIRA

View raw message