Details

      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

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        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).

        Show
        bryanthompson bryanthompson added a comment - 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).

          People

          • Assignee:
            bryanthompson bryanthompson
            Reporter:
            bryanthompson bryanthompson
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: