Details

    • Type: Improvement
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Static Query Optimizer
    • Labels:
      None

      Description

      There are are quite a few things that should be improved in the ASTStaticJoinOptimizer:

      • The code currently does not make use of implicit join constraints imposed via "FILTER ?x=?y" constructs (which are used by the RTO, see PartitionedJoinGroup.canJoinUsingConstraints)
      • The selectivity of FILTERs is not considered, s.t. in some cases joins with unselective filters are imposed before joining with SPNs carrying selective FILTER nodes
      • The optimizer should be moved in the pipeline, being aligned with the ASTJoinGroupOrderOptimizer (which, as an intermediate step, gives a nice partitioned set of nodes that could be freely reordered)

        Issue Links

          Activity

          Hide
          bryanthompson bryanthompson added a comment -

          Many join group optimizations require us to implement a non-blocking hash join operator to avoid increasing the latency to the first result for queries that use a LIMIT.

          Show
          bryanthompson bryanthompson added a comment - Many join group optimizations require us to implement a non-blocking hash join operator to avoid increasing the latency to the first result for queries that use a LIMIT.

            People

            • Assignee:
              michaelschmidt michaelschmidt
              Reporter:
              michaelschmidt michaelschmidt
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: