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

SPARQL UPDATE should use a SolutionSetStream backed by native memory for DELETE/INSERT+WHERE to avoid OOM

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: BLAZEGRAPH_2_2_0
    • Component/s: SPARQL UPDATE
    • Labels:
      None

      Description

      SPARQL UPDATE currently runs the query into a MutableTupleQueryResult and then replays it for both the DELETE and the INSERT aspect of a DELETE/INSERT+WHERE query. This ensures proper isolation of the query and the mutation. However, this means that large result sets can be materialized on the Java heap.

      This ticket is to replace the use of the MutableTupleQueryResult with a SolutionSetStream backed by the native heap (memstore).

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: