The SPARQL Update parser currently parses all update queries into a single UpdateRequest object which holds them in memory. Instead the parser should insert queries into something like a Sink<Update>. Additionally it should put the quads from INSERT_DATA and DELETE_DATA into a Sink<Quad> instead of an ArrayList.
This should allow the creation of a streaming update parser, which could be combined with
JENA-309 to have full streaming into an underlying transactional store and the ability to handle arbitrarily large INSERT_DATA or DELETE_DATA queries (to the limits of the transaction system).