[
https://issues.apache.org/jira/browse/SOLR-8462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski updated SOLR-8462:
----------------------------------
Description:
Currently, the /stream request handler reports errors by adding an "EXCEPTION"
name/value pair on a tuple in the TupleStream where the error arose. The
"value" in this name/value pair is the message attached to the exception.
This works well in most instances, however it could be better in a few ways:
1.) Not all exceptions have messages. For instance, {{NullPointerExceptions}}
and other run time exceptions fall into this category. This causes the /stream
handler to return the relatively unhelpful value:
{"EXCEPTION":null,"EOF":true}. The /stream handler should make sure the
exception has a message, and if not, it should report some other information
about the error (exception class name?).
2.) There are some common error cases that can arise from mis-use of the API.
For instance, if the 'expr' parameter is missing. Detecting and handling these
cases specifically would allow users to get back clearer, more useful error
messages.
was:
Currently, the /stream request handler reports errors by adding an "EXCEPTION"
name/value pair on a tuple in the TupleStream where the error arose. The
"value" in this name/value pair is the message attached to the exception.
This works well in most instances, however not all exceptions have messages.
{{NullPointerExceptions}} and other run time exceptions are often in this
group. This causes the /stream handler to return the relatively unhelpful
value: {"EXCEPTION":null,"EOF":true}
The purpose of this JIRA is to change error handling in the /stream handler, so
that more helpful information is returned when the handled exception has no
message.
This information could simply be the name of the exception that was received.
Or it could be something more involved. Not sure what would be the most
helpful here.
> Improve error reporting for /stream handler
> -------------------------------------------
>
> Key: SOLR-8462
> URL: https://issues.apache.org/jira/browse/SOLR-8462
> Project: Solr
> Issue Type: Improvement
> Affects Versions: Trunk
> Reporter: Jason Gerlowski
> Priority: Trivial
> Fix For: Trunk
>
> Attachments: SOLR-8462.patch
>
>
> Currently, the /stream request handler reports errors by adding an
> "EXCEPTION" name/value pair on a tuple in the TupleStream where the error
> arose. The "value" in this name/value pair is the message attached to the
> exception.
> This works well in most instances, however it could be better in a few ways:
> 1.) Not all exceptions have messages. For instance,
> {{NullPointerExceptions}} and other run time exceptions fall into this
> category. This causes the /stream handler to return the relatively unhelpful
> value: {"EXCEPTION":null,"EOF":true}. The /stream handler should make sure
> the exception has a message, and if not, it should report some other
> information about the error (exception class name?).
> 2.) There are some common error cases that can arise from mis-use of the API.
> For instance, if the 'expr' parameter is missing. Detecting and handling
> these cases specifically would allow users to get back clearer, more useful
> error messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
