[
https://issues.apache.org/jira/browse/SOLR-18446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18116361#comment-18116361
]
David Smiley commented on SOLR-18446:
-------------------------------------
yes; I actually worked on the comma-delimited support and probably added the
"collection" param in the first place. It was added in the context of time
routed aliases, where there is some ambiguity around scope & routing. I'm all
for comma delimited list in the path still; I just don't like the collection
parameter. As for helping HttpSolrCall make a specific routing choice when
there are a multitude of options -- I have advocated for expanding on the path
to use a lesser-known URL spec feature called matrix parameters. I brought
this up on our dev list
https://lists.apache.org/thread/fb2mh93v18rowfzxzg52bp46jgmf86r3 but didn't get
a warm response to the idea. Honestly I'm fed up with the matter and am
tempted to take matters into my own hands, only stoppable by a veto.
> Remove "collection" param routing support in HttpSolrCall
> ---------------------------------------------------------
>
> Key: SOLR-18446
> URL: https://issues.apache.org/jira/browse/SOLR-18446
> Project: Solr
> Issue Type: Improvement
> Components: Server
> Reporter: David Smiley
> Priority: Blocker
>
> The URL path alone should govern which collection receives a
> collection-scoped request. Node level APIs (e.g. admin) don't count here.
> Consequently, the "collection" parameter should be removed or altered in
> semantics from the present day.
> It'd be harmless if the collection param were to assist in disambiguating a
> core name in the path, if we want that, as that prevents a 404.
> It'd be harmless if the collection param disambiguated multiple possibilities
> if the path implied more than one (i.e. was an alias to multiple collections
> or was comma delimited).
> It's acknowledged and out-of-scope that there are parameters like "shards"
> affecting how a handler (e.g. SearchHandler) dispatch distributed work. The
> scope of the current ticket is basically HttpSolrCall resolving to a "core"
> locally or remotely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
