[
https://issues.apache.org/jira/browse/SOLR-7988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723208#comment-14723208
]
ludovic Boutros commented on SOLR-7988:
---------------------------------------
Well, quite true :)
The question I would have here is:
Do you want to keep this handler and perhaps others, which need the collection
name on the admin path ?
If yes, I can imagine an exclusion in the _CloudSolrClient_
if no, we just need to choose another path and register the handler(s) with
this new path (but that would break a sort of compatibility...)
> LukeRequest on default path is broken with CloudSolrClient
> ----------------------------------------------------------
>
> Key: SOLR-7988
> URL: https://issues.apache.org/jira/browse/SOLR-7988
> Project: Solr
> Issue Type: Bug
> Components: SolrJ
> Affects Versions: 5.3
> Reporter: ludovic Boutros
>
> SOLR-7757 breaks the default access on the _LukeRequestHandler_ (/admin/luke)
> with _CloudSolrClient_.
> See the following commit :
> https://svn.apache.org/viewvc/lucene/dev/branches/branch_5x/solr/solrj/src/java/org/apache/solr/client/solrj/impl/CloudSolrClient.java?r1=1694556&r2=1694555&pathrev=1694556
> The name of the collection is not added to the request URL and therefore we
> get a 404 error in the response.
> Defining the _LukeRequestHandler_ with another path in the _solrconfig_ is a
> workaround but it's quite annoying.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
