[
https://issues.apache.org/jira/browse/SOLR-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506178#comment-14506178
]
Joel Bernstein commented on SOLR-7441:
--------------------------------------
Let's get this fixed for 5.2. I remember running across an error that didn't
make it to the logs. Later when I went back to see if I could an error that was
not appearing in the logs I wasn't able to find one.
Is the fl error not ending up in the logs, or just being logged in a
complicated way?
In parallel mode you also end up with a json error on the worker node, as well
as the original error on the search node.Would be good propagate the original
error from the search node to the worker node to the client so you don't have
dig around in the logs.
> Streaming aggregation error messages could use some improvement
> ---------------------------------------------------------------
>
> Key: SOLR-7441
> URL: https://issues.apache.org/jira/browse/SOLR-7441
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 5.1
> Reporter: Erick Erickson
> Priority: Minor
>
> 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]
