2. Summary
  3. Files
  4. Support
  5. Report Spam
  6. Create account
  7. Log in

Ticket #356 (closed defect: fixed)

Opened 22 months ago

Last modified 21 months ago

Query not terminated by error

Reported by: thompsonbry Owned by: thompsonbry
Priority: major Milestone: Query
Component: Bigdata SAIL Version: BIGDATA_RELEASE_1_0_0
Keywords: Cc: gjdev, mrpersonick, thompsonbry

Description

A circumstance has been observed where a SPARQL query encounters an error but the error is not observed by the thread draining the query solutions. This issue is documented at [1]. A separate ticket (this one) has been opened for the problem in reporting the query error back to the client.

[1] https://sourceforge.net/apps/trac/bigdata/ticket/355

Change History

Changed 21 months ago by thompsonbry

  • status changed from new to closed
  • resolution set to fixed

I believe that this issue has been resolved. The Sesame CloseableIteration? requires hasNext() to invoke close() when the iteration is exhausted. The bigdata iterator pattern will report back the error no later than close (and earlier unless there are solutions which were already buffered before the error such that the error was not yet observed by the iterator since it has not reached back to its source).

Note: See TracTickets for help on using tickets.

© 2013 SourceForge. All Rights Reserved. SourceForge is a Dice Holdings, Inc. company   Terms of Use - Privacy Policy - Cookies/Opt Out