[
https://issues.apache.org/jira/browse/JENA-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705479#comment-14705479
]
Andy Seaborne commented on JENA-1011:
-------------------------------------
This does not affect NT and NQ at all -- completely different, single threaded,
code.
There was inconsistent implementation of "hasNext" in the piped iterator - it
can throw an exception according to the tests but that is not what the Iterator
contract says. I think I've fixed this.
Turtle and RDF/XML correctly bracket parser runs with StreamRDF start/finish;
ReaderJsonLD and ReaderTriX did not. This should not matter due to other calls
but it did.
> RiotReader.createIteratorTriples causes NPE for some syntaxes.
> --------------------------------------------------------------
>
> Key: JENA-1011
> URL: https://issues.apache.org/jira/browse/JENA-1011
> Project: Apache Jena
> Issue Type: Bug
> Components: RIOT
> Affects Versions: Jena 3.0.0
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
> Attachments: ExampleIteratorParsing.java
>
>
> Some syntaxes (e.g. JSON-LD, TRIX) cause the async thread parsing to throw a
> null pointer exception.
> Changing {{RiotReader::parse}} to:
> {noformat}
> RDFDataMgr.parse(dest, in, baseIRI, lang);
> {noformat}
> then causes "Producer dead".
> Adding {{out.start}}/{{out.finish}} nesting in {{createIteratorTriples}}
> causes "Pipe closed".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
