[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396986#comment-13396986
]
Stephen Allen commented on JENA-261:
------------------------------------
It is a little non-intuitive that SERVICE SILENT returns an empty row on
failure, but there's a fairly easy work-around in your query, just filter them
out if you don't want to handle it in the client code:
SELECT * WHERE {
{SERVICE silent <A> { ?m a <foo> }}
UNION
{SERVICE silent <B> { ?m a <foo> }}
filter ( bound(?m) )
}
> QueryIterService returns an empty solution on exception
> -------------------------------------------------------
>
> Key: JENA-261
> URL: https://issues.apache.org/jira/browse/JENA-261
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: ARQ 2.9.0, ARQ 2.9.1
> Reporter: Claude Warren
> Attachments: JENA-261_patch.txt
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> in nextStage() when a RuntimeException is caught and the 'silent' parameter
> has been set, a QueryIterSingleton is created. This results in an empty
> solution being returned. I think the proper action would be to return a
> QueryIterNullIterator so that the empty result is not returned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
