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

Jan Høydahl commented on SOLR-17568:
------------------------------------

[~dsmiley] 

Preparing for first release with logchange tool, I found that this issue adds 
two CHANGES.txt entries for the same JIRA, under different headings:

 
{code:java}
Optimizations
---------------------
* SOLR-17568: The CLI bin/solr export tool now contacts the appropriate nodes 
directly for data instead of proxying through one.
 (David Smiley)

Other Changes
---------------------
* SOLR-17568: SolrCloud no longer reroutes/proxies a core request to another 
node if not found locally. (David Smiley) {code}
[https://github.com/apache/solr/pull/2885/files#diff-cdd1ae1b418ea74ca689c6e68e61f4e5b4c6f77f6408a4e6cf76ed8421b24d09]

If this was not on purpose, please clean up the CHANGES file before we generate 
CHANGES.md next week.

 

> Remove remote *core* query in SolrCloud mode
> --------------------------------------------
>
>                 Key: SOLR-17568
>                 URL: https://issues.apache.org/jira/browse/SOLR-17568
>             Project: Solr
>          Issue Type: Task
>          Components: SolrCloud
>            Reporter: David Smiley
>            Assignee: David Smiley
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 10.0
>
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> If a SolrCloud node receives a request with a local core name (not a 
> collection name), it will be handled by the local core.  But it even works 
> with a remote core -- it'll be forwarded to the node that has a core by that 
> name.  I think there's no use-case for that -- users should only reference 
> collections (any node) or a core on a node where it's known to exist (on that 
> node!) since it's a core not a cluster concept.  This got my attention 
> because the functionality requires iterating all collections.  This would 
> happen for any request when a collection/core is not known to the node (and 
> may not exist at all).  I shall remove this in Solr 10.
> There is exactly one test for this functionality -- 
> {{org.apache.solr.cloud.AbstractBasicDistributedZk2TestBase#addAndQueryDocs}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to