lucene-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/SOLR-4431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628174#comment-13628174
] 

Shawn Heisey commented on SOLR-4431:
------------------------------------

With apologies to Hoss for jumping in and possibly speaking for him:

bq. 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.

A "typical" tomcat/glassfish/whatever user will never look at jetty.xml.  They would have
no reason to - they aren't using jetty.  They will use the .war file and possibly a few of
the miscellaneous solr/lucene jars, either in-place in the solr download or by copying them
to a new location.  If someone who uses the included jetty (patched as you propose) were to
talk to a tomcat user, they might say "go to http://localhost:8983/solr/cloud" to that user.
 If that tomcat user had never looked at jetty.xml or had never updated their tomcat configuration
to match the jetty example, the URL would fail.

bq. I'm a bit confused by this, the patch does NOT change the URL structure. It's just 3 simple
302 redirects.

What I have proposed there is a completely separate change, requiring its own Jira, which
I have created as SOLR-4700.  The idea would be that going forward, we would use http://host:port/solr/XXX/corename
as the base URL for clients instead of http://host:port/solr/corename as we do now.  I don't
have a good suggestion for XXX at the moment.  If we did that, then you could still create
a collection or core named "cloud" and that would not get in the way of a convenience URL.
 At that point the convenience URLs could be baked into Solr code rather than provided by
the servlet container.
                
> Developer Curb Appeal: easier URLs for Cloud UI, Admin, etc.
> ------------------------------------------------------------
>
>                 Key: SOLR-4431
>                 URL: https://issues.apache.org/jira/browse/SOLR-4431
>             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 http://172.16.10.236:8983/solr/#/~cloud
> 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: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message