[
https://issues.apache.org/jira/browse/SOLR-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671195#comment-13671195
]
Shawn Heisey commented on SOLR-4715:
------------------------------------
After a little bit of thought, I'm thinking the reason the ResponseParser
object is final is so that there are no thread visibility problems, because it
can't ever change. The following ideas would require removing that final
modifier and adding an object for a shared RequestWriter.
For CloudSolrServer: If no requests have been processed yet, then the
LBHttpSolrServer object will not yet have any internal HttpSolrServer objects,
so passing through setParser and setRequestWriter calls should be perfectly
safe. We can block these methods once the first request gets processed, or we
can just pass them through and rely on the following:
For LBHttpSolrServer, we can do one of three things with setParser and
setRequestWriter if there are any ServerWrapper objects (and therefore
HttpSolrServer objects): 1) Throw an exception. 2) Ignore the request. 3)
Make the requested change on all HttpSolrServer objects.
> 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
>
> CloudSolrServer (and LBHttpSolrServer) do not allow the user to set
> underlying HttpSolrServer and HttpClient settings.
--
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]
