For <1>, hmmm. Apart from redesigning…. You can create
a single-shard collection. The trick is to co-locate one replica
in the “otherCollection” on _every_ Solr instance your main
collection is on. You’ll have to look at the ZK collection information
to know exactly what the otherCore name is, it’l
Hi Erick,
Thanks for replying. I know that I should deal at collection level in
SolrCloud mode and leave dealing with cores to SolrCloud. I am also aware
of collection aliasing feature.
However, the plugins that I am trying to migrate to SolrCloud have some
usecases like following:
1. One of the
This kind of seems like an XY problem. Why do you want to get to the other core?
If you need to run the same query on multiple cores… you shouldn’t be thinking
that way, think “collections” rather than cores. And you can use “collection
aliasing”
(see the Collections API CREATEALIAS command) to al
Hi,
I have one custom Solr plugin that uses following logic to access some
other core present on the same Solr instance.
request.getCore().getCoreContainer().getCore(otherCoreName) where request
is an object of type SolrQueryRequest
This works fine in master-slave mode.
Now if try to use the sa
