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

Aaron LaBella updated SOLR-12790:
---------------------------------
    Description: 
moved ServerWrapper logic in LBHttpSolrClient.request(...) to a method to allow 
subclasses to 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).

 

Can someone please commit this as soon as possible.  I don't necessarily need 
it to be back-ported, having in 7.4.1 would suffice.

Thanks!

  was:moved ServerWrapper logic in LBHttpSolrClient.request(...) to a method to 
allow subclasses to 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).


> 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 to 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).
>  
> Can someone please commit this as soon as possible.  I don't necessarily need 
> it to be back-ported, having in 7.4.1 would suffice.
> Thanks!



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

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

Reply via email to