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

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

GitHub user dkuppitz opened a pull request:

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

    TINKERPOP-1681 Multiple hasId's are or'd into GraphStep

    https://issues.apache.org/jira/browse/TINKERPOP-1681
    
    Fixed folding of multiple `hasId()`'s into `GraphStep`.
    
    VOTE: +1

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

    $ git pull https://github.com/apache/tinkerpop TINKERPOP-1681

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

    https://github.com/apache/tinkerpop/pull/617.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 #617
    
----
commit 063118e9d7b65cff82e74c5db47e64524a833e92
Author: Daniel Kuppitz <daniel_kupp...@hotmail.com>
Date:   2017-05-28T13:41:34Z

    Fixed folding of multiple `hasId()` into `GraphStep`.

----


> Multiple hasId's are or'd into GraphStep
> ----------------------------------------
>
>                 Key: TINKERPOP-1681
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1681
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.2.4
>            Reporter: Daniel Kuppitz
>            Assignee: Daniel Kuppitz
>
> From the dev mailing list:
> {noformat}
>     @Test
>     public void testHasId() {
>         final TinkerGraph graph = TinkerGraph.open();
>         Vertex a = graph.addVertex(T.label, "A");
>         Vertex b = graph.addVertex(T.label, "B");
>         List<Vertex> vertices = 
> graph.traversal().V().hasId(a.id()).hasId(b.id()).toList();
>         Assert.assertTrue(vertices.isEmpty());
>     }
> {noformat}
> The test fails as the both vertices are returned.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to