[
https://issues.apache.org/jira/browse/JENA-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490241#comment-13490241
]
Andy Seaborne commented on JENA-330:
------------------------------------
The patch doesn't align in the parser due to deprecating, then ripping out, the
SPARQL Submission transition support. I didn't feel I understood it well
enough to manualy apply it.
I have added the null graph store/ transaction additions.
I wonder if the best approach is to focus on the SPARQL Graph Store Protocol
for bulk addition of data. We could have POST to a graph be streaming triples
and POST to the dataset itself for streaming quads.
> Streaming support for SPARQL Update queries and streaming support for quads
> in INSERT DATA / DELETE DATA queries
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JENA-330
> URL: https://issues.apache.org/jira/browse/JENA-330
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: Stephen Allen
> Assignee: Stephen Allen
> Priority: Minor
> Attachments: config-null.ttl, JENA-330_20121016.patch,
> TestLargeUpdates.java
>
>
> 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).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
