You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Stephen Allen (Commented) (JIRA)" <ji...@apache.org> on 2012/03/26 02:46:28 UTC

[jira] [Commented] (JENA-205) Streaming results for CONSTRUCT queries

    [ https://issues.apache.org/jira/browse/JENA-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238022#comment-13238022 ] 

Stephen Allen commented on JENA-205:
------------------------------------

I've added execConstructTriples() to ARQ to provide streaming support for both local and remote query execution (revision 1305184).

Last thing left to do is add streaming to Fuseki.  The bulk of the work here would involve modifying existing or creating new RDF writers to accept Iterator<Triple> instead of a Model.


                
> 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