[
https://issues.apache.org/jira/browse/JENA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238215#comment-13238215
]
Andy Seaborne commented on JENA-205:
------------------------------------
Looks good.
I moved the Sink-to-queue into the general library.
More of an observation; not a proposal to do anything:
The Turtle/TriG parsers could provide a pull interface if they parsed small
blocks, that is from subject up to a DOT, and served those out of a queue,
making them like N-Triples and Q-Quads. Then the pull arrangement would not
need an intermediate thread. The potential downside of no buffering above the
HTTP level is avoided because the tokenizer has a large buffer.
But this would be a bit of reorganization of the TurtleBase parser --
triplesSameSubject would need to be turned into a capturing loop that may
affect performance of push mode.
> Streaming results for CONSTRUCT queries
> ---------------------------------------
>
> Key: JENA-205
> URL: https://issues.apache.org/jira/browse/JENA-205
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ, Fuseki
> Reporter: Stephen Allen
> Assignee: Stephen Allen
> Priority: Minor
>
> It would be useful to have CONSTRUCT queries that streamed results. An
> additional method on QueryExecution that returned an Iterator<Statement> (or
> something similar to that [1]) would provide the necessary access.
> Implementationwise, the application of Bindings to the CONSTRUCT template is
> already streaming, we would simply need to perform a distinct operation on
> the Triples that are created. We could use a DistinctDataNet to get
> semi-streaming with spill-to-disk functionality.
> Additionally, for this to be useful for Fuseki, we also need an RDF/XML
> serializer that can operate on an Iterator<Statement> instead of a Model.
> [1] Prefix mappings would probably be nice for serializers that consume this
> iterator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
