lucene-dev mailing list archives

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


Shawn Heisey commented on SOLR-4431:

-1 here too, can't think of any additional reasons beyond those Hoss has stated.

Everything except this patch's specific tie to jetty would be solved if we could put the API
to access cores and collections into its own url path, such as /api/corename (horrible name,
just for illustration purposes).  That is an idea with its own problems, though.  The current
URL scheme is so widely used that there'd be no way we could remove backward compatibility
until at least 6.0.  Note: I actually think this would be a good move, but I would not expect
to see a lot of support for it.

> 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