[ 
https://issues.apache.org/jira/browse/SOLR-11982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16393271#comment-16393271
 ] 

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

I think it should be a single parameter that can address the different types of 
preference, not different parameters one for each type. In general I like the 
syntax discussed here so far (I have that concern of the pipe I mentioned 
before). I also feel it falls into the "shards" family of parameters. 
{{shards}} determines the replicas to which the distributed query should be 
sent, {{shards.info}} tells users which replicas responded a distributed query, 
etc. as I said before, I think it is close to what's discussed in SOLR-10880 
and naming should be consistent. I'm ok with changing the word "sort" if you 
think that can confuse users. Do you think something like {{shards.preference}} 
would be better [~elyograg]?
{quote} I don't think it needs to since the client, whatever it is, has full 
control over where to send the query.
{quote}
Unless they are using CloudSolrClient... but yes, in that case users can choose 
not to use it. In any case, I think that can be left to another Jira. We should 
include a big note in the docs though.

> Add support for indicating preferred replica types for queries
> --------------------------------------------------------------
>
>                 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: 7.3, master (8.0)
>            Reporter: Ere Maijala
>            Priority: Minor
>              Labels: patch-available, patch-with-test
>         Attachments: SOLR-11982-preferReplicaTypes.patch, SOLR-11982.patch, 
> SOLR-11982.patch, SOLR-11982.patch, SOLR-11982.patch
>
>
> It would be nice to have the possibility to easily sort the shards in the 
> preferred order e.g. by replica type. The attached patch adds support for 
> {{shards.sort}} parameter that allows one to sort e.g. PULL and TLOG replicas 
> first with \{{shards.sort=replicaType:PULL|TLOG }}(which would mean that NRT 
> replicas wouldn't be hit with queries unless they're the only ones available) 
> and/or to sort by replica location (like preferLocalShards=true but more 
> versatile).



--
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