[
https://issues.apache.org/jira/browse/SOLR-17568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-17568:
--------------------------------
Description:
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}}
was:
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}}
> 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
> Priority: Major
>
> 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]
