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

Yang Xia closed TINKERPOP-1475.
-------------------------------
    Resolution: Won't Do

Closing given 
[discussion|https://lists.apache.org/thread/om2m0phg25s83529p9w0gldmcxz7578h] - 
it can be reopened if there is expectation that there will be active work on 
this item.

> MatchPredicateStrategy can be inlined optimized.
> ------------------------------------------------
>
>                 Key: TINKERPOP-1475
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1475
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: process
>    Affects Versions: 3.2.2
>            Reporter: Marko A. Rodriguez
>            Priority: Major
>
> Given the work in TINKERPOP-1456, it will be possible to inline 
> "has()"-pullouts to a stronger extent for ALL filters, not just 
> "has()"-chains.
> {code}
> match(
>   a.has(z).filter(x.y)
>   ...
> )
> {code}
> can become:
> {code}
> a.has(z).filter(x.y).match(...)
> {code}
> The, via {{InlineFilterStrategy}}, children of {{filter()}} can be analyzed 
> for inlining. 
> {code}
> a.has(z).x.y.match(...)
> {code}
> The point of all this is to try and inline filters as much as possible so 
> they can be picked up by provider-specific graph- and vertex-centric index 
> strategies.
> {{MatchPredicateStrategy}} will need to be a POST to {{InlineFilterStrategy}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to