I've never seen the email you quote before nor does it appear to be in the mailing list archives, are you sure you actually sent it to the list?
The PipedRDFIterator is supposed to handle errors sensibly, a minimal reproducible test case with sample data where it does not would be helpful Also what version of ARQ are you using? Thanks, Rob On 9/30/13 3:22 PM, "Norman Walsh" <[email protected]> wrote: >Norman Walsh <[email protected]> writes: >> I'm setting up a PipedRDFIterator to load triples from a large file. >> The trouble is, the file in question contains a syntax error so the >> "writing thread" falls over. Sometimes when this happens, .hasNext() >> on the PipedRDFIterator loops forever. Even calling .close() doesn't >> help because .hasNext() only looks to see if the writer has been >> closed. >> >> Suggestions, please? > >No thoughts? > > Be seeing you, > norm > >-- >Norman Walsh <[email protected]> | There has never been an unexpectedly >http://nwalsh.com/ | short debugging period in the history > | of computers.--Steven Levy
