lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Commented] (SOLR-4431) Developer Curb Appeal: easier URLs for Cloud UI, Admin, etc.
Date Tue, 09 Apr 2013 18:04:18 GMT


Hoss Man commented on SOLR-4431:


a) this patch would change the behaviour only of the example jetty server, causing solr to
(knowingly!) behave radically different if you deployed to a different servlet container.

2) as explicitly mentioned before, this change would cause problems for people trying to create
solr cores (or handlers in the default solr core) named "cloud" (or any other names that get
taken up by other aliases like this that might get added if we go down this road)...

bq. switching these UI URLs from things like "/~cloud" to "/cloud" would cause problems for
anyone who might want to have a collection named "cloud" 

The included Admin UI is a nice to have, but improving it's ease of use or prettiness must
not come at the expense of reduced configurability or expressiveness of the underlying API

If people want an admin UI for solr that has short and pretty URLs then it should be something
deployed as an independent war (or written in ruby or whatever)

> Developer Curb Appeal: easier URLs for Cloud UI, Admin, etc.
> ------------------------------------------------------------
>                 Key: SOLR-4431
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>    Affects Versions: 4.1
>            Reporter: Mark Bennett
>         Attachments: SOLR-4431.patch
> Currently the URL to get the cloud UI is
> The path and anchor portion is very strange: "/solr/#/~cloud"
> Ideally it would just be "/cloud"
> Or even just "/", and if it's in "cloud mode", take the admin to the right place.
> If there's some internal important structural reason for "/solr", "#" and "~cloud" sections,
perhaps each would need to be addressed.
> Another option would be to possibly put something the default Jetty xml file to handle
this as some type of redirect or registered handle.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message