You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Aaron LaBella (JIRA)" <ji...@apache.org> on 2018/09/20 16:46:00 UTC

[jira] [Updated] (SOLR-12790) move ServerWrapper logic in LBHttpSolrClient to a method to allow subclasses override. expose other fields as protected

     [ https://issues.apache.org/jira/browse/SOLR-12790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aaron LaBella updated SOLR-12790:
---------------------------------
    Attachment: SOLR-12790-1.patch

> move ServerWrapper logic in LBHttpSolrClient to a method to allow subclasses override.  expose other fields as protected
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-12790
>                 URL: https://issues.apache.org/jira/browse/SOLR-12790
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrJ
>    Affects Versions: 5.0
>            Reporter: Aaron LaBella
>            Priority: Blocker
>              Labels: ready-to-commit
>         Attachments: SOLR-12790-1.patch
>
>
> moved ServerWrapper logic in LBHttpSolrClient.request(...) to a method to allow subclasses override.  expose other fields as protected.  This allows sub-classes to apply different logic other than round-robin, when using the LBHttpSolrClient class.  In my case, we wish to use an algorithm that *only* uses the first / primary server unless it is unavailable, and then it uses the secondary server(s).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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