You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Munendra S N (Jira)" <ji...@apache.org> on 2020/03/19 14:13:00 UTC

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

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

Munendra S N edited comment on SOLR-14345 at 3/19/20, 2:12 PM:
---------------------------------------------------------------

I was thinking to handle this in Parser but then, extracting {{error}} shouldn't be part of parser and would create lot of duplicate code.
Other approach is to create duplicate of InputStream and process it using BinaryResponseParser and required parser. This kind of overkill and also expensive
[~hossman] [~dsmiley] [~mkhl] [~ichattopadhyaya] Any suggestion here, that could handle it generically including NoOpResponseParser?


was (Author: munendrasn):
I was thinking to handle this in Parser but then, extracting {{error}} shouldn't be part of parser and would create lot of duplicate code
[~hossman] [~dsmiley] [~mkhl] [~ichattopadhyaya] Any suggestion here, that could handle it generically including NoOpResponseParser?

> 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
>            Assignee: Munendra S N
>            Priority: Major
>         Attachments: SOLR-14345.patch, 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