You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Joel Bernstein (JIRA)" <ji...@apache.org> on 2015/07/03 18:24:05 UTC

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

     [ https://issues.apache.org/jira/browse/SOLR-7441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joel Bernstein updated SOLR-7441:
---------------------------------
    Attachment: SOLR-7441.patch

Patch with all tests passing

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org