Uploaded image for project: 'TinkerPop'
  1. TinkerPop
  2. TINKERPOP-2532

MaxBarrierSize of NoOpBarrierStep should be accessible

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: 3.4.10
    • Fix Version/s: 3.5.0, 3.4.11
    • Component/s: process
    • Labels:
      None

      Description

      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).

       

      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.

        Attachments

          Activity

            People

            • Assignee:
              spmallette Stephen Mallette
              Reporter:
              rngcntr Florian G
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: