[
https://issues.apache.org/jira/browse/SOLR-9378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719447#comment-17719447
]
Chris M. Hostetter commented on SOLR-9378:
------------------------------------------
SOLR-13595 would also be trivially fixed by this change(since ShardsAugmenter
would no longer depend on the {{shard.url}} param
> Avoid sending the shard.url parameter in shard requests
> -------------------------------------------------------
>
> Key: SOLR-9378
> URL: https://issues.apache.org/jira/browse/SOLR-9378
> Project: Solr
> Issue Type: Improvement
> Components: search, SolrCloud
> Reporter: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 6.2, 7.0
>
>
> The shard.url parameter contains a list of all replicas for a shard. One of
> those is chosen by the HttpShardHandler to execute the request. So, it is
> used only within the context of processing request on a distributor node as a
> special storage for a list of replicas urls between the prep and execution
> phase of HttpShardHandler. There is no real need to send this parameter down
> to the chosen shard.
> However, Hoss pointed out to me that removing this would break
> ShardAugmenterFactory so we need to figure out if/how we can do this.
> Personally, I don't think it is at all useful to write down *all* replicas
> with the document without telling which replica really served the query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
