You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2014/02/03 11:44:11 UTC
[jira] [Comment Edited] (JENA-267) SPARQL JSON Parser is not
streaming
[ https://issues.apache.org/jira/browse/JENA-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889374#comment-13889374 ]
Rob Vesse edited comment on JENA-267 at 2/3/14 10:42 AM:
---------------------------------------------------------
There are a few TODOs left in the code some of which at least need to be implemented.
Particularly the one in {{preParse()}} where we should be deriving the variables available in the case where the initial buffering finds the {{results}} element but does not exhaust it i.e. the case where {{results}} shows up before the {{header}} so we don't know precisely the variables defined in the results but can derive them from the results we've cached
was (Author: rvesse):
There are a few TODOs left in the code some of which at least need to be implemented. Particularly the one in {{preParse()}} where we should be deriving the variables available in the case where the initial buffering finds all results without seeing the header yet.
> SPARQL JSON Parser is not streaming
> -----------------------------------
>
> Key: JENA-267
> URL: https://issues.apache.org/jira/browse/JENA-267
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: ARQ 2.9.1
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Labels: json, sparql
>
> The current SPARQL JSON parser in ARQ parses the JSON by parsing the entire response into a in-memory data structure and then iterating over that. So for large results it is trivial to hit an OutOfMemory exception.
> This task is to reimplement the SPARQL JSON parser to be fully streaming in its implementation in line with all the other results parsers
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)