[
https://issues.apache.org/jira/browse/JENA-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Allen updated JENA-329:
-------------------------------
Description:
As a result of JENA-205, streaming results are now available for CONSTRUCT
queries. However there can be duplicate triples in the iterator. This task is
to allow Fuseki to stream back results, while at the same time performing a
distinct operation.
The fix would be to modify SPARQL_Query to use
QueryExecution.execConstructTriples() and filter the results through a
DistinctDataNet<Triple> as they are being streamed back to the client.
This also requires RDFWriter implementations that can accept Iterator<Triple>
instead of Model.
was:
As a result of JENA-205, streaming results are now available for CONSTRUCT
queries. However there can be duplicate triples in the iterator. This task is
to allow Fuseki to stream back results, while at the same time performing a
distinct operation.
The fix would be to modify SPARQL_Query to use
QueryExecution.execConstructTriples() and filter the results through a
DistinctDataNet<Triple> as they are being streamed back to the client.
> Add streaming CONSTRUCT results to Fuseki
> -----------------------------------------
>
> Key: JENA-329
> URL: https://issues.apache.org/jira/browse/JENA-329
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Stephen Allen
>
> As a result of JENA-205, streaming results are now available for CONSTRUCT
> queries. However there can be duplicate triples in the iterator. This task
> is to allow Fuseki to stream back results, while at the same time performing
> a distinct operation.
> The fix would be to modify SPARQL_Query to use
> QueryExecution.execConstructTriples() and filter the results through a
> DistinctDataNet<Triple> as they are being streamed back to the client.
> This also requires RDFWriter implementations that can accept Iterator<Triple>
> instead of Model.
--
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
