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

ASF subversion and git services commented on SOLR-12217:
--------------------------------------------------------

Commit 53345cb1cd1eb54e33af65046825f624ba3cadd1 in lucene-solr's branch 
refs/heads/branch_8x from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=53345cb ]

SOLR-12217: Support shards.preference in SolrJ for individual shard requests 
(#984)


> Add support for shards.preference in SolrJ for single shard cases
> -----------------------------------------------------------------
>
>                 Key: SOLR-12217
>                 URL: https://issues.apache.org/jira/browse/SOLR-12217
>             Project: Solr
>          Issue Type: New Feature
>          Components: SolrJ, streaming expressions
>    Affects Versions: master (9.0), 8.4
>            Reporter: Tomas Eduardo Fernandez Lobbe
>            Assignee: Houston Putman
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> SOLR-11982 Added support for {{shards.preference}}, a way to define the 
> sorting of replicas within a shard by preference (replica types/location). 
> This only works on multi-shard cases. We should add support for the case of 
> single shards when using CloudSolrClient. We should also add support for 
> Streaming Expressions, since they also send requests to individual shards.
> *NOTE:* This Jira doesn't cover the single-sharded collections cases when not 
> using the CloudSolrClient or Streaming Expressions (i.e. if you do a 
> non-streaming _curl_ request to a random node in the cluster, the 
> {{shards.preference}} parameter is not considered in the case of single 
> shards collections).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to