[
https://issues.apache.org/jira/browse/TINKERPOP-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876549#comment-16876549
]
ASF GitHub Bot commented on TINKERPOP-1619:
-------------------------------------------
spmallette commented on pull request #1153: TINKERPOP-1619 Fix optional() with
TinkerGraphComputer
URL: https://github.com/apache/tinkerpop/pull/1153
https://issues.apache.org/jira/browse/TINKERPOP-1619
All tests pass with `docker/build.sh -t -i`
VOTE +1
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> TinkerGraphComputer worker count affects OptionalStep query results
> -------------------------------------------------------------------
>
> Key: TINKERPOP-1619
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1619
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.3.0
> Reporter: Ted Wilmes
> Priority: Major
>
> I found that when I bump the worker count up to 4 on my local box, the dedup
> nested in the optional appears to not be handled correctly.
> {code}
> gremlin> g = TinkerFactory.createModern().traversal()
> ==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
> gremlin> g.withComputer(Computer.compute().workers(3)).V(1,
> 2).optional(bothE().dedup())
> ==>e[9][1-created->3]
> ==>e[7][1-knows->2]
> ==>e[8][1-knows->4]
> ==>v[2]
> gremlin> g.withComputer(Computer.compute().workers(4)).V(1,
> 2).optional(bothE().dedup())
> ==>e[9][1-created->3]
> ==>e[7][1-knows->2]
> ==>e[7][1-knows->2]
> ==>e[8][1-knows->4]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
