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

Simple optionals are not optimized in sub-selects

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: BIGDATA_RELEASE_1_3_0
    • Fix Version/s: None
    • Component/s: Query Plan Generator
    • Labels:
      None

      Description

      Simple optionals are an optional group with a single triple pattern and no filters. Such optionals use a different query plan than a complex optional. For the simple optional, the JOIN is marked as "OPTIONAL". For a complex optional, we build a hash index, run the joins, and then join against the hash index using an OPTIONAL join.

      The problem is probably that we are not descending into the sub-select when we do the analysis of simple optionals.

        Attachments

          Activity

            People

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

              Dates

              Created:
              Updated: