[ https://issues.apache.org/jira/browse/SOLR-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14635758#comment-14635758 ]
ASF subversion and git services commented on SOLR-7441: ------------------------------------------------------- Commit 1692193 from [~joel.bernstein] in branch 'dev/trunk' [ https://svn.apache.org/r1692193 ] SOLR-7441:Improve overall robustness of the Streaming stack: Streaming API, Streaming Expressions, Parallel SQL > 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, 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org