lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Bennett (JIRA)" <>
Subject [jira] [Commented] (SOLR-4431) Developer Curb Appeal: easier URLs for Cloud UI, Admin, etc.
Date Wed, 10 Apr 2013 17:20:17 GMT


Mark Bennett commented on SOLR-4431:

This patch proposes 3 simple URLs redirects:
* Send /admin to /solr/#/
* Send /cores to /solr/#/~cores
* Send /cloud to /solr/#/~cloud

Points that might not be clear:
* This doesn't not attempt to change the overall URL structure, it's not trying to get rid
of the # or ~ stuff; the earlier comments explained why those needed to be there.
* It's just 3 simple 302 redirects, for 3 specific URLs.
* It does a redirect (NOT a rewrite), so it's quite clear what it's doing for you
* Only for those EXACT URLs.  If you put "/admin/foobar" or "/cloud9" it doesn't match.
* These are very prominently shown at the top of jetty.xml, so really to see.

Response to objections:

Uwe's objections:
* " Solr 4 is a new major veryion" - agreed
* ".., old style URLs need no redirection" - that's not what this patch does
* "If somebody needs them, it is easy to modify the webapp / webserver to forward to forward
in that case." - actually it wasn't easy, due to to ivy and jetty issues.  But this patch
fixes that, and gives 3 nice examples, so now it would be easy.

Hoss's objections:
* "a) this patch would change the behaviour only of the example jetty server," - yes, via
a very visible configuration in jetty.xml
* "... causing solr to (knowingly!) behave radically different" - radically different?? It
only matches those 3 exact URL fragments?
* "... if you deployed to a different servlet container." - but then you wouldn't use jetty.xml,
or at least you'd have to rename and modify the file, and you'd certainly see the redirects,
and could choose to retain them or not.
* "2) ... this change would cause problems for people trying to create solr cores (or handlers
in the default solr core) named "cloud" - But it only matches "c l o u d", and if you didn't
like it, it's at the top of jetty.xml and can easily be removed, .  And for holding out for
that pristine possibility that somebody might someday do, 100% of users are denied convenience
* "(or any other names that get taken up by other aliases like this that might get added if
we go down this road)..." - the redirects are very visible and easily removed.  And I actually
think it gives a nice example of what people could do privately on their own projects.  Prior
to this patch, redirects weren't working at all in our default Solr.
* "The included Admin UI is a nice ... must not come at the expense of reduced configurability
or expressiveness of the underlying API URLs." - It doesn't.  Not using rewrites, and every
easy to remove it.
* "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)" - Realistically this may
never happen.  Meanwhile, other open source offerings have nice simple URLs (though don't
have the rich UI)

Shawn's objections:
* "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 ..." - I wonder if some of folks
misunderstood what this patch does - it's NOT doing internal rewrites, and it's not doing
partial matching.
* "The current URL scheme is so widely used that there'd be no way we could remove backward
compatibility ..." - I'm a bit confused by this, the patch does NOT change the URL structure.
 It's just 3 simple 302 redirects.
> 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