You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2024/11/19 07:01:00 UTC

[jira] [Created] (SOLR-17568) Remove remote *core* query in SolrCloud mode

David Smiley created SOLR-17568:
-----------------------------------

             Summary: Remove remote *core* query in SolrCloud mode
                 Key: SOLR-17568
                 URL: https://issues.apache.org/jira/browse/SOLR-17568
             Project: Solr
          Issue Type: Task
      Security Level: Public (Default Security Level. Issues are Public)
          Components: SolrCloud
            Reporter: David Smiley
            Assignee: David Smiley


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.  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: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org