You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tinkerpop.apache.org by "Florian G (Jira)" <ji...@apache.org> on 2021/03/12 12:30:00 UTC

[jira] [Created] (TINKERPOP-2532) MaxBarrierSize of NoOpBarrierStep should be accessible

Florian G created TINKERPOP-2532:
------------------------------------

             Summary: MaxBarrierSize of NoOpBarrierStep should be accessible
                 Key: TINKERPOP-2532
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2532
             Project: TinkerPop
          Issue Type: Improvement
          Components: process
            Reporter: Florian G


We would like to use the `maxBarrierSize` parameter of `NoOpBarrierStep`s as a parameter for batch queries in JanusGraph to improve the performance of storage interactions (see JanusGraph Issue [2514|https://github.com/JanusGraph/janusgraph/issues/2514]).

 

The purpose of the `NoOpBarrierStep` is to aggregate intermediate results before passing them to the next step in the pipeline. Aligning the size of batch queries with the barrier size helps improving the responsiveness of queries in this scenario.

 

To do so, we need to access the parameter `maxBarrierSize`. I propose to introduce a public getter method. As of now, the `maxBarrierSize` is already semi-publicly accessible because it is contained in the `toString()` representation of the step.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)