[
https://issues.apache.org/jira/browse/TINKERPOP-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko A. Rodriguez closed TINKERPOP-1210.
-----------------------------------------
Resolution: Implemented
Assignee: Marko A. Rodriguez
Fix Version/s: 3.2.0-incubating
> Provide an OrderLimitStep as an optimization.
> ---------------------------------------------
>
> Key: TINKERPOP-1210
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1210
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.1.1-incubating
> Reporter: Marko A. Rodriguez
> Assignee: Marko A. Rodriguez
> Fix For: 3.2.0-incubating
>
>
> The pattern {{order().limit()}} is used alot. Currently, the way we implement
> this is by barrier'ing everything at {{order()}} and then sorting the entire
> barrier before sending it along to {{limit()}} for clipping.
> What we should be doing (especially in OLAP), is to continually order the
> barrier ({{SortedMap}}-style) and clip it (at least heuristically -- not via
> bulk) to the {{limit()}}-size. Then, pass the barrier off to {{limit()}} for
> the final clipping.
> We may be able to get away with making it so {{OrderGlobalStep}} has a
> {{limit}}-field that it can use to automatically clip its barrier.
> Likewise, this will also work for {{DedupGlobalStep}} and
> {{dedup().limit(10)}}-type traversals.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
