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).
|Field||Original Value||New Value|
|Fix Version/s||BLAZEGRAPH_2_2_0 [ 10302 ]|
|Assignee||Brad Bebee [ beebs ]||michaelschmidt [ michaelschmidt ]|
|Status||Open [ 1 ]||Accepted [ 10101 ]|
|Status||Accepted [ 10101 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Status||Resolved [ 5 ]||In Review [ 10100 ]|
|Resolution||Done [ 10000 ]|
|Status||In Review [ 10100 ]||Done [ 10000 ]|