Re: SolrCloud request routing URL structure

2025-01-14 Thread David Smiley
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

Re: SolrCloud request routing URL structure

2025-01-14 Thread David Smiley
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

Re: SolrCloud request routing URL structure

2025-01-14 Thread Pierre Salagnac
I'm not a big fan of matrix parameters to identify the resource we want to target. To me, as a guideline, the path of the URL is to target a resource, which in the Solr case is a collection/shard/core and a handler. Then parameters, or the query part of the URL, give other details like the action

Re: SolrCloud request routing URL structure

2025-01-10 Thread Jason Gerlowski
Hi, Sorry for the late reply on this thread. I've been trying to take time to understand the problem a little better before chiming in. (FWIW I think this would be a great discussion for the Meetup next week?) I think much of what you described makes sense in a v1 context, but v2 has some nice b

Re: SolrCloud request routing URL structure

2025-01-02 Thread David Smiley
I'd like to move forward on this soon. A colleague expressed concern about matrix-params being obscure so perhaps should be avoided because of that. However, to me it seems their use is well fitting to the problem. Also, I estimate this path will have relatively low impact on the codebase with r

Re: SolrCloud request routing URL structure

2024-12-10 Thread David Smiley
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

Re: SolrCloud request routing URL structure

2024-12-10 Thread Chris Hostetter
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 node return 404, but before doing that it forcibly refreshes