Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-1181

Consequently exploit new built-in projection capabilities of HashIndexOp

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Done
    • Priority: Highest
    • Resolution: Done
    • Affects Version/s: BIGDATA_RELEASE_1_5_0
    • Fix Version/s: BLAZEGRAPH_2_0_0
    • Component/s: Query Plan Generator
    • Labels:
      None

      Description

      The HashIndexOp now offers means to compute distinct projections over a set of variable (see ticket BLZG-1163). This is exposed via method AST2BOpUtility.addHashIndexOp(). Currently, this method is used for SPARQL 1.1 subqueries (AST2BOpUtility.addSparql11Subquery) as well as for join groups (AST2BOpUtility.addSubgroup).

      However, there are some more positions in the code where we calculate hash indices and where the built-in projection capabilites might be useful. Consider the following methods:


      - AST2BOpUtility.addNamedSubqueryInclude()
      - AST2BOpUtility.addExistsSubqueryFast()
      - AST2BOpUtility.doMergeJoin()

      Decide whether it makes sense to pass in projection variables in these positions. Even if not, it might be desirable to call method addHashIndexOp() (or a slightly modified version thererof) instead of the duplicated code blocks for hash index construction).

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: