[
https://issues.apache.org/jira/browse/SOLR-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14506408#comment-14506408
]
Erick Erickson commented on SOLR-7441:
--------------------------------------
Nothing came out in the server log, and the client log was unhelpful (not quite
sure what it was now...). This was just using a CloudSolrStream....
I'm not at all sure when opening a stream and expecting back a TupleStream but
get an error message how it would be decoded into a log message though, so just
dumping it into the server log would certainly be a step forward.
> 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]
