[
https://issues.apache.org/jira/browse/SOLR-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701440#comment-17701440
]
ASF subversion and git services commented on SOLR-16694:
--------------------------------------------------------
Commit a50cb06b2f3086f23678ad1bf1d58f90521807bd in solr's branch
refs/heads/main from Tomas Eduardo Fernandez Lobbe
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=a50cb06b2f3 ]
SOLR-16694: Shortcut Http2SolrClient mimeType check for default response parse
(#1447)
> Shortcut Http2SolrClient mimeType check for default response parse
> ------------------------------------------------------------------
>
> Key: SOLR-16694
> URL: https://issues.apache.org/jira/browse/SOLR-16694
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Tomas Eduardo Fernandez Lobbe
> Priority: Minor
> Attachments: screenshot-1.png, screenshot-2.png
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Http2SolrClient has some logic to get the list of content types supported by
> the response parser, parse those from String into {{ContentType}} objects to
> then get the mimeType of those and put them on a Set, to later check against
> the response content type.
> In practice, most users of Http2SolrClient (including Solr itself) will be
> using javabin with the BinaryResponseParser, for which we know the exact
> mimeType that will accept. We could avoid the logic I've described above for
> cases where the response parser is the default one
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
