[jira] [Updated] (TINKERPOP-2499) PathRetractionStrategy returns inconsistent results when match() is not detected as the final step

[Stephen Mallette (Jira)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette updated TINKERPOP-2499:

Labels: breaking  (was: )

> PathRetractionStrategy returns inconsistent results when match() is not 
> detected as the final step
> --
>
> Key: TINKERPOP-2499
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2499
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.4.9
>Reporter: Stephen Mallette
>Priority: Major
>  Labels: breaking
>
> This issue comes from TINKERPOP-2481 where it was originally noted that 
> perhaps {{IdentityRemovalStrategy}} had something to do with the following:
> {code}
> gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
> ==>[]
> ==>[]
> gremlin> 
> g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> gremlin> 
> g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold()
> gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold().path()
> ==>[v[1],v[1],v[2],[a:v[1],b:v[2]],a=v[1]]
> ==>[v[1],v[1],v[2],[a:v[1],b:v[2]],b=v[2]]
> ==>[v[1],v[1],v[4],[a:v[1],b:v[4]],a=v[1]]
> ==>[v[1],v[1],v[4],[a:v[1],b:v[4]],b=v[4]]
> {code}
> but it is not a good idea to fix the behavior of one strategy by way of 
> another so {{PathRetractionStrategy}} needs to get a bit smarter.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (TINKERPOP-2499) PathRetractionStrategy returns inconsistent results when match() is not detected as the final step

[Stephen Mallette (Jira)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette updated TINKERPOP-2499:

Description: 
This issue comes from TINKERPOP-2481 where it was originally noted that perhaps 
{{IdentityRemovalStrategy}} had something to do with the following:

{code}
gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
==>[]
==>[]
gremlin> 
g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
gremlin> 
g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold()
gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold().path()
==>[v[1],v[1],v[2],[a:v[1],b:v[2]],a=v[1]]
==>[v[1],v[1],v[2],[a:v[1],b:v[2]],b=v[2]]
==>[v[1],v[1],v[4],[a:v[1],b:v[4]],a=v[1]]
==>[v[1],v[1],v[4],[a:v[1],b:v[4]],b=v[4]]
{code}

but it is not a good idea to fix the behavior of one strategy by way of another 
so {{PathRetractionStrategy}} needs to get a bit smarter.

  was:
This issue comes from TINKERPOP-2481 where it was originally noted that perhaps 
{{IdentityRemovalStrategy}} had something to do with the following:

{code}
gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold()
gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
==>[]
==>[]
gremlin> 
g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
gremlin> 
g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
{code}

but it is not a good idea to fix the behavior of one strategy by way of another 
so {{PathRetractionStrategy}} needs to get a bit smarter.


> PathRetractionStrategy returns inconsistent results when match() is not 
> detected as the final step
> --
>
> Key: TINKERPOP-2499
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2499
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.4.9
>Reporter: Stephen Mallette
>Priority: Major
>
> This issue comes from TINKERPOP-2481 where it was originally noted that 
> perhaps {{IdentityRemovalStrategy}} had something to do with the following:
> {code}
> gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
> ==>[]
> ==>[]
> gremlin> 
> g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> gremlin> 
> g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold()
> gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold().path()
> ==>[v[1],v[1],v[2],[a:v[1],b:v[2]],a=v[1]]
> ==>[v[1],v[1],v[2],[a:v[1],b:v[2]],b=v[2]]
> ==>[v[1],v[1],v[4],[a:v[1],b:v[4]],a=v[1]]
> ==>[v[1],v[1],v[4],[a:v[1],b:v[4]],b=v[4]]
> {code}
> but it is not a good idea to fix the behavior of one strategy by way of 
> another so {{PathRetractionStrategy}} needs to get a bit smarter.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (TINKERPOP-2499) PathRetractionStrategy returns inconsistent results when match() is not detected as the final step

[Stephen Mallette (Jira)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette updated TINKERPOP-2499:

Summary: PathRetractionStrategy returns inconsistent results when match() 
is not detected as the final step  (was: PathRetractionStrategy returns 
inconsistent results when identity() follows match())

> PathRetractionStrategy returns inconsistent results when match() is not 
> detected as the final step
> --
>
> Key: TINKERPOP-2499
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2499
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.4.9
>Reporter: Stephen Mallette
>Priority: Major
>
> This issue comes from TINKERPOP-2481 where it was originally noted that 
> perhaps {{IdentityRemovalStrategy}} had something to do with the following:
> {code}
> gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
> ==>[]
> ==>[]
> gremlin> 
> g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> gremlin> 
> g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> {code}
> but it is not a good idea to fix the behavior of one strategy by way of 
> another so {{PathRetractionStrategy}} needs to get a bit smarter.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (TINKERPOP-2499) PathRetractionStrategy returns inconsistent results when match() is not detected as the final step

[Stephen Mallette (Jira)]

 [ 
https://issues.apache.org/jira/browse/TINKERPOP-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Mallette updated TINKERPOP-2499:

Description: 
This issue comes from TINKERPOP-2481 where it was originally noted that perhaps 
{{IdentityRemovalStrategy}} had something to do with the following:

{code}
gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold()
gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
==>[]
==>[]
gremlin> 
g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
gremlin> 
g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
{code}

but it is not a good idea to fix the behavior of one strategy by way of another 
so {{PathRetractionStrategy}} needs to get a bit smarter.

  was:
This issue comes from TINKERPOP-2481 where it was originally noted that perhaps 
{{IdentityRemovalStrategy}} had something to do with the following:

{code}
gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
==>[]
==>[]
gremlin> 
g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
gremlin> 
g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
==>[a:v[1],b:v[2]]
==>[a:v[1],b:v[4]]
{code}

but it is not a good idea to fix the behavior of one strategy by way of another 
so {{PathRetractionStrategy}} needs to get a bit smarter.


> PathRetractionStrategy returns inconsistent results when match() is not 
> detected as the final step
> --
>
> Key: TINKERPOP-2499
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2499
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: process
>Affects Versions: 3.4.9
>Reporter: Stephen Mallette
>Priority: Major
>
> This issue comes from TINKERPOP-2481 where it was originally noted that 
> perhaps {{IdentityRemovalStrategy}} had something to do with the following:
> {code}
> gremlin> g.V().match(__.as("a").out("knows").as("b")).unfold()
> gremlin> g.V().match(__.as("a").out("knows").as("b")).identity()
> ==>[]
> ==>[]
> gremlin> 
> g.withStrategies(IdentityRemovalStrategy.instance()).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> gremlin> 
> g.withoutStrategies(PathRetractionStrategy).V().match(__.as("a").out("knows").as("b")).identity()
> ==>[a:v[1],b:v[2]]
> ==>[a:v[1],b:v[4]]
> {code}
> but it is not a good idea to fix the behavior of one strategy by way of 
> another so {{PathRetractionStrategy}} needs to get a bit smarter.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)