[
https://issues.apache.org/jira/browse/TINKERPOP-2865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Mallette closed TINKERPOP-2865.
---------------------------------------
Fix Version/s: 3.7.0
3.5.6
3.6.3
Resolution: Done
> Add has steps injected by PartitionStrategy at the end of the filter
> --------------------------------------------------------------------
>
> Key: TINKERPOP-2865
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2865
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.5.5
> Reporter: Stephen Mallette
> Assignee: Stephen Mallette
> Priority: Major
> Fix For: 3.7.0, 3.5.6, 3.6.3
>
>
> Currently, {{PartitionStrategy}} will add the {{HasStep}} for the partition
> key right after the step that triggers is, like:
> {code}
> g.V().hasLabel("person") -> g.V().has("_p","A").hasLabel("person")
> {code}
> It seems better in these cases to be slightly less invasive to the traversal
> and push the partition has to the end to therefore preserve the order of the
> previous filters:
> {code}
> g.V().hasLabel("person") -> g.V().hasLabel("person").has("_p","A")
> {code}
> This change probably matters most to {{Vertex}} and {{Edge}} read steps.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
