[
https://issues.apache.org/jira/browse/SOLR-17591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17911047#comment-17911047
]
Jason Gerlowski commented on SOLR-17591:
----------------------------------------
bq. I dislike the "collection" param. It's redundant with the path, adds
confusion or possible a security concern
Agreed. And your concerns go double for the 'qt' parameter, which historically
you could use to switch the endpoint entirely! Solr's outgrown these IMO and
we should consider removing support for these query parameters.
To the behavior Siju reported: the inconsistency is jarring. I don't have any
guesses offhand why that'd be the case, but it's worth looking into IMO.
> SolrJ : CloudSolrClient does not honor collection aliasing
> ----------------------------------------------------------
>
> Key: SOLR-17591
> URL: https://issues.apache.org/jira/browse/SOLR-17591
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Reporter: Siju Varghese
> Priority: Minor
>
> Requests using CloudSolrClient fail with http 400 / could not find collection
> when querying a collection with its aliased name.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
