On Tue, Jan 14, 2025 at 12:48 PM David Smiley wrote:
> Any way, for V1, CloudSolrClient sends a parameter like this:
>_stateVer_=collection1:3
> It's used for distributed ClusterState cache invalidation by
> CloudSolrClient.[1]. It's a list of collections and their versions
> (consider that a
Jason said:
> There's not currently a "shard-level" path for querying, but other
> APIs currently exist at the
> "/collections/someColl/shards/someShardName" path, so it's only a
> small leap to offering querying there.
>
So Jersey/OpenAPI will have no problem with all the core handlers being
add
..
> > > X-Solr-Collection: bar
> > >
> > > * bar is expected to be the name of a collection
> > > * if bar isn't a valid collection name, just return 404,
> > >don't bother checking for a local SolrCore named bar
> > >
> > > Examp
gt; * bar is expected to be the name of a collection
> > * if bar isn't a valid collection name, just return 404,
> >don't bother checking for a local SolrCore named bar
> > * foo is expected to be the name of a specific (local) replica
> >of the collection
> * if a SolrCore named foo doesn't exist on the current node *OR*
> if a SolrCore named foo does exist, but isn't a replica of
>collection bar, just return 404, don't bother picking an
>arbitrary replica of collection bar
>
> Example #4
>
> GET /solr/yak/selec
On Tue, Dec 10, 2024 at 5:36 PM Chris Hostetter
wrote:
>
> I don't disagree with any of your points. If anything i think the problem
> is more egregious then you characterize it (especially in the case of
> requests for specific replicas that have been (re)moved -- IIRC not only
> does the Solr
if a SolrCore named foo does exist, but isn't a replica of
collection bar, just return 404, don't bother picking an
arbitrary replica of collection bar
Example #4
GET /solr/yak/select?...
X-Solr-Collection: bar
X-Solr-Replica: foo
* neither hint matches path, return 404
In a number of circumstances, CloudSolrClient and various parts of Solr
(distributed search, distributed indexing), will create a request routed to
a specific core in SolrCloud. But the routing is almost always done
plainly, with the URL path like /solr/foo/handler and SolrCloud
(specifically Http
