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

Barrier steps provide unexpected results in Gremlin OLAP

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0-incubating
    • Fix Version/s: 3.2.0-incubating
    • Component/s: process
    • Labels:
      None

      Description

      When a Barrier is called in OLAP, it should force an iteration and not just TraverserExecutor.toProcessTraversers. That is, it should act as if the traverser (even if its local) should be message passed.

      This has always existed, we just never had a test case for the situation. Dead simple fix.

        Activity

        Hide
        okram Marko A. Rodriguez added a comment -

        This is actually not a "dead simple fix." It requires the use of GraphComputer.Memory to create a distributed lock for all Barrier steps. Not crazy, just not so easy it should be a fix for 3.1.0. The following branch origin/TINKERPOP3-951 has the test case the fails in OLAP and passes in OLTP.

        Show
        okram Marko A. Rodriguez added a comment - This is actually not a "dead simple fix." It requires the use of GraphComputer.Memory to create a distributed lock for all Barrier steps. Not crazy, just not so easy it should be a fix for 3.1.0. The following branch origin/ TINKERPOP3-951 has the test case the fails in OLAP and passes in OLTP.

          People

          • Assignee:
            okram Marko A. Rodriguez
            Reporter:
            okram Marko A. Rodriguez
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development