We're updating the issue view to help you get more done. 

Support background parsing/concurrent reading of query results

Description

Currently, when doing a query or export, HTTPRepository builds up the entire result in memory before giving an iterator back to the user. This is non-scalable. We should look at implementing a background-parsing strategy similar to what SPARQLRepository supports. On a more general level we can probably merge a lot of the functionalities of HTTPRepository and SPARQLRepository. One radical approach would be to completely get rid of Sesame's XML transaction format, and instead just work with SPARQL Updates.

Environment

None

Status

Assignee

JeenB

Reporter

JeenB

Labels

None

Fix versions

Priority

Critical