[
https://issues.apache.org/jira/browse/TINKERPOP-2503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette updated TINKERPOP-2503:
----------------------------------------
Description:
With TINKERPOP-2499 we made traversal results from {{match()}} more consistent
but it came with the cost of not being as aggressive at trimming unneeded
labels. It would be good to get back to supporting patterns we once had (which
were much too strictly defined and relied on the execution of other strategies
to work) where we could properly recognize:
{code}
match(__.as("a").out("knows").as("b")).select('a')
match(__.as("a").out("knows").as("b")).dedup('a')
{code}
and perhaps even various calls to {{path()}} which has always completely exited
{{PathRetractionStrategy}}. If this gets done for 3.5.0, then Upgrade Docs for
"match() Consistency" should be edited
was:
With TINKERPOP-2499 we made traversal results from {{match()}} more consistent
but it came with the cost of not being as aggressive at trimming unneeded
labels. It would be good to get back to supporting patterns we once had (which
were much too strictly defined and relied on the execution of other strategies
to work) where we could properly recognize:
{code}
match(__.as("a").out("knows").as("b")).select('a')
match(__.as("a").out("knows").as("b")).dedup('a')
{code}
and perhaps even various calls to {{path()}} which has always completely exited
{{PathRetractionStrategy}}
> Implement look-ahead on PathRetractionStrategy
> ----------------------------------------------
>
> Key: TINKERPOP-2503
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2503
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.4.9
> Reporter: Stephen Mallette
> Priority: Major
>
> With TINKERPOP-2499 we made traversal results from {{match()}} more
> consistent but it came with the cost of not being as aggressive at trimming
> unneeded labels. It would be good to get back to supporting patterns we once
> had (which were much too strictly defined and relied on the execution of
> other strategies to work) where we could properly recognize:
> {code}
> match(__.as("a").out("knows").as("b")).select('a')
> match(__.as("a").out("knows").as("b")).dedup('a')
> {code}
> and perhaps even various calls to {{path()}} which has always completely
> exited {{PathRetractionStrategy}}. If this gets done for 3.5.0, then Upgrade
> Docs for "match() Consistency" should be edited
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
