[
https://issues.apache.org/jira/browse/TINKERPOP-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357159#comment-16357159
]
Florian Hockmann commented on TINKERPOP-1882:
---------------------------------------------
To be honest, I didn't think about the {{LazyBarrierStrategy}} but that makes
queries like {{g.V(a).out().valueMap().limit(123)}} of course a much smaller
problem.
{quote}Without the {{barrier(2500)}} the traversal wouldn't add any extra
processing that wasn't necessary, correct?
{quote}
Yes, that was exactly my intention with this ticket.
However, shouldn't the end result be
{{g.V(a).out().limit(123).barrier(2500).valueMap()}}? So, I guess this new
strategy should ideally be applied prior to the {{LazyBarrierStrategy}}.
> Apply range and limit steps as early as possible
> ------------------------------------------------
>
> Key: TINKERPOP-1882
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1882
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.7, 3.3.1
> Reporter: Florian Hockmann
> Priority: Minor
>
> For a traversal like
> {{g.V(a).out().valueMap().limit(123)}}
> we can simply move the {{limit()}} to the left so we get:
> {{g.V(a).out().limit(123).valueMap()}}
> This avoids unnecessary database lookups.
> We should create a strategy that moves the {{limit}} and the {{range}} step
> like this to _the left_ for all {{map}} steps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
