[
https://issues.apache.org/jira/browse/SOLR-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602805#comment-14602805
]
Joel Bernstein commented on SOLR-7441:
--------------------------------------
[[email protected]], I've had a chance to review the patch. I think there are
some things in there that we can use. The idea of having a field in the Tuple
to hold the error makes it easy to propagate errors through the tiers. The
trick will be getting the error added to an outgoing tuple in all the different
places in the stack where an error can originate. Below is a preliminary list
of the areas where exceptions may originate in the stack. Some of the areas are
handled by the patch you provided.
1) Error from the */select* handler before the stream is started
(JSONResponseWriter)
2) Error from the */export* handler before the stream is started
(SortingResponseWriter)
3) Error midstream from the */select* handler;
4) Error midstream from the */export* handler.
5) Error from the Streaming API, before the request is sent. (*Non-parallel
mode*)
6) Error from the Streaming API, before the request is sent. (*In Parallel mode
or on the worker*)
7) Error from the SQL Parser (SQLHandler)
> Improve overall robustness of the Streaming stack: Streaming API, Streaming
> Expressions, Parallel SQL
> -----------------------------------------------------------------------------------------------------
>
> Key: SOLR-7441
> URL: https://issues.apache.org/jira/browse/SOLR-7441
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 5.1
> Reporter: Erick Erickson
> Assignee: Joel Bernstein
> Priority: Minor
> Attachments: SOLR-7441.patch, SOLR-7441.patch
>
>
> It's harder than it could be to figure out what the error is when using
> Streaming Aggregation. For instance if you specify an fl parameter for a
> field that doesn't exist it's hard to figure out that's the cause. This is
> true even if you look in the Solr logs.
> I'm not quite sure whether it'd be possible to report this at the client
> level or not, but it seems at least we could repor something more helpful in
> the Solr logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
