Tomás Fernández Löbbe commented on SOLR-11982:

Thanks [~emaijala], this looks really good. Again, I'm trying to unify the API 
with the work done in SOLR-10880. SOLR-10880 attempts to filter the replicas 
that can be used for resolving a query using {{shards.filter}}. It feels like 
what you are doing here is sorting the replicas, to prefer some over others. 
How do you feel about using the a parameter like {{shards.sort}}, and making 
the value something like {{replicaType:PULL,replicaType:TLOG}}? {{local}} could 
actually be just a keyword of this new parameter, and someone could do:
{{...&shards.sort=replicaType:PULL,local}} meaning "use replicas of type PULL 
if available, otherwise prefer local cores, otherwise any replica}}. In the 
future, the replica tags, as defined in SOLR-10880 could also be used for 
sorting and not only for filtering (i.e. 
If so, we can deprecate {{preferLocalShards}}

> Add support for preferReplicaTypes parameter
> --------------------------------------------
>                 Key: SOLR-11982
>                 URL: https://issues.apache.org/jira/browse/SOLR-11982
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: master (8.0), 7.3
>            Reporter: Ere Maijala
>            Priority: Minor
>              Labels: patch-available, patch-with-test
>         Attachments: SOLR-11982-v2.patch, SOLR-11982-v3.patch, 
> SOLR-11982.patch
> It would be nice to have the possibility to easily prefer certain replica 
> types in a similar fashion to preferLocalShards. I'll be coming up with a 
> patch that allows one to specify e.g. preferReplicaTypes=PULL,TLOG which 
> would mean that NRT replicas wouldn't be hit with queries unless they're the 
> only ones available.

This message was sent by Atlassian JIRA

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

Reply via email to