Hi Gus, I haven't yet had a chance review the ticket, but I will try to get to it soon. I have a pretty big backlog of work on the Streaming API, Streaming Expressions and Parallel SQL stack, but error handling is an important part of the stack.
Joel Bernstein http://joelsolr.blogspot.com/ On Mon, May 25, 2015 at 4:19 PM, Gus Heck (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14558501#comment-14558501 > ] > > Gus Heck commented on SOLR-7441: > -------------------------------- > > Will this make 5.2? Is there anything you need from me? > > > 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 > > 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: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
