[SOLR-7441] Improve overall robustness of the Streaming stack: Streaming API, Streaming Expressions, Parallel SQL

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.1
• Fix Version/s: 6.0
• Assignee: Joel Bernstein
• Reporter: Erick Erickson
• Created: 21/Apr/15 23:35
• Updated: 08/Oct/19 14:51
• Resolved: 09/Aug/15 20:55

Description

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.

Issue Links

• is related to: SOLR-7621 Frequent 500 error IOExceptions from StreamingExpressions
• is related to: SOLR-7472 SortingResponseWriter does not log fl parameters that don't exist.