[jira] [Commented] (SOLR-14345) Error messages are not properly propagated with non-default response parsers

["Munendra S N (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-14345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061433#comment-17061433 ] 

Munendra S N commented on SOLR-14345:
-------------------------------------

 [^SOLR-14345.patch] 
Initial patch bit hacky
* Works with Json parsers. Xml and Javabin parsers doesn't have this problem
* haven't handled Http2SolrClient
* This approach doesn't work for NoOpResponseParser

Essentially the problem is the way error is extracted from parsed response. Error is always assumed to be NamedList which might not be the case with other parsers.

> Error messages are not properly propagated with non-default response parsers
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-14345
>                 URL: https://issues.apache.org/jira/browse/SOLR-14345
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Munendra S N
>            Priority: Major
>         Attachments: SOLR-14345.patch
>
>
> Default {{ResponsParseer}} is {{BinaryResponseParser}}. when non-default response parser is specified in the request then, the error message is propagated to user. This happens in solrCloud mode.
> I came across this problem when working on adding some test which uses {{SolrTestCaseHS}} but similar problem exists with SolrJ client
> Also, same problem exists in both HttpSolrClient and Http2SolrClient



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org