You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2016/10/26 13:55:59 UTC
[jira] [Updated] (TINKERPOP-1529) LazyBarrierStrategy is too
agressive
[ https://issues.apache.org/jira/browse/TINKERPOP-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kuppitz updated TINKERPOP-1529:
--------------------------------------
Description:
There are scenarios where {{LazyBarrierStrategy}} changes the semantics of a traversal:
{noformat}
gremlin> g = TinkerFactory.createModern().traversal()
==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
gremlin> g.V().store("a").out().select("a")
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
This is actually not the result of {{store()}}, this is {{aggregate()}}. The expected result for {{store()}} would be:
{noformat}
==>[v[1]]
==>[v[1]]
==>[v[1]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
Another issue, which should probably go into another ticket, is this:
{noformat}
gremlin> g.withoutStrategies(LazyBarrierStrategy).V().store("a").out().select("a")
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
That's it, the console is hanging at this point. Looks like {{PathRetractionStrategy}} is the remaining troublemaker. With both strategies excluded, we get the expected result:
{noformat}
gremlin> g.withoutStrategies(LazyBarrierStrategy, PathRetractionStrategy).V().store("a").out().select("a")
==>[v[1]]
==>[v[1]]
==>[v[1]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
was:
There are scenarios where {{LazyBarrierStrategy}} changes the semantics of a traversal:
{noformat}
gremlin> g = TinkerFactory.createModern().traversal()
==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
gremlin> g.V().store("a").out().select("a")
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
This is actually not the result of {{store()}}, this is {{aggregate()}}. The expected result for {{store()}} would be:
{noformat}
==>[v[1]]
==>[v[1],v[2]]
==>[v[1],v[2],v[3]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4],v[5]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
Another issue, which should probably go into another ticket, is this:
{noformat}
gremlin> g.withoutStrategies(LazyBarrierStrategy).V().store("a").out().select("a")
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
That's it, the console is hanging at this point. Looks like {{PathRetractionStrategy}} is the remaining troublemaker. But even if both strategies are excluded, the result is still not what I would expect:
{noformat}
gremlin> g.withoutStrategies(LazyBarrierStrategy, PathRetractionStrategy).V().store("a").out().select("a")
==>[v[1]]
==>[v[1]]
==>[v[1]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4]]
==>[v[1],v[2],v[3],v[4],v[5],v[6]]
{noformat}
> LazyBarrierStrategy is too agressive
> ------------------------------------
>
> Key: TINKERPOP-1529
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1529
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.2.3
> Reporter: Daniel Kuppitz
>
> There are scenarios where {{LazyBarrierStrategy}} changes the semantics of a traversal:
> {noformat}
> gremlin> g = TinkerFactory.createModern().traversal()
> ==>graphtraversalsource[tinkergraph[vertices:6 edges:6], standard]
> gremlin> g.V().store("a").out().select("a")
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> {noformat}
> This is actually not the result of {{store()}}, this is {{aggregate()}}. The expected result for {{store()}} would be:
> {noformat}
> ==>[v[1]]
> ==>[v[1]]
> ==>[v[1]]
> ==>[v[1],v[2],v[3],v[4]]
> ==>[v[1],v[2],v[3],v[4]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> {noformat}
> Another issue, which should probably go into another ticket, is this:
> {noformat}
> gremlin> g.withoutStrategies(LazyBarrierStrategy).V().store("a").out().select("a")
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> {noformat}
> That's it, the console is hanging at this point. Looks like {{PathRetractionStrategy}} is the remaining troublemaker. With both strategies excluded, we get the expected result:
> {noformat}
> gremlin> g.withoutStrategies(LazyBarrierStrategy, PathRetractionStrategy).V().store("a").out().select("a")
> ==>[v[1]]
> ==>[v[1]]
> ==>[v[1]]
> ==>[v[1],v[2],v[3],v[4]]
> ==>[v[1],v[2],v[3],v[4]]
> ==>[v[1],v[2],v[3],v[4],v[5],v[6]]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)