[
https://issues.apache.org/jira/browse/SOLR-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-4715:
-------------------------------
Attachment: SOLR-4715-incomplete.patch
The null parser wasn't the reason for all the failures. It was me trying to
replace the deprecated HttpComponents call (EntityUtils.getContentCharSet) that
gets the character set from the response.
Updated patch, still incomplete.
Is there a valid use case for having a null parser? The test for
LBHttpSolrServer implies that there is.
> CloudSolrServer does not provide support for setting underlying server
> properties
> ---------------------------------------------------------------------------------
>
> Key: SOLR-4715
> URL: https://issues.apache.org/jira/browse/SOLR-4715
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.3
> Reporter: Hardik Upadhyay
> Assignee: Shawn Heisey
> Labels: solr, solrj
> Attachments: SOLR-4715-incomplete.patch, SOLR-4715-incomplete.patch
>
>
> CloudSolrServer (and LBHttpSolrServer) do not allow the user to set
> underlying HttpSolrServer and HttpClient settings without arcane java
> enchantments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
