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

SPARQL UPDATE should not materialize RDF Values

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Bigdata RDF Database
    • Labels:
      None

      Description

      Materializing RDF Values from IVs is expensive and is not necessary for SPARQL UPDATE operations. The code paths should be reworked to avoid this operation whenever possible. This may be somewhat tricky when truth maintenance is involved if the existing APIs are not aligned for that.

      1. The DELETE/INSERT operator should not materialize IVs as Values. We need an alternative ASTConstructIterator which does ISPO constructs and then directly pumps the ISPOs into the assertion or retraction interface of the Sail. That interface might currently require Statements, in which case we have more work to do.

      2. CLEAR should run at a lower level. Even when TM is used (but not if isolation is used).

      3. DROP might have different semantics for isolation if we see DROP ALL. E.g., remove and re-register the triple store/quad store rather than recording delete markers for all tuples in all indices.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated: