[
https://issues.apache.org/jira/browse/TINKERPOP-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302414#comment-17302414
]
ASF GitHub Bot commented on TINKERPOP-2532:
-------------------------------------------
spmallette merged pull request #1406:
URL: https://github.com/apache/tinkerpop/pull/1406
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
> Priority: Trivial
>
> 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)
