[
https://issues.apache.org/jira/browse/SOLR-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423286#comment-13423286
]
Hoss Man commented on SOLR-3633:
--------------------------------
bq. is difference between having something "global" (i.e. /solr/zookeeper)
instead of relying on some specific core (i.e. /solr/collection1/logs) a
difficult change?
for some things (like /system and /logs) it's probably doable ... but it will
definitely take some time and refactoring ... i don't think we should rush it
or make plans assuming it can be done quickly, because you never know where
that code might have a small, crucial, assumption about hte availability of a
core.
and honestly: the "zero core" situation probably isn't a place where it really
makes a lot of sense to focus a lot of effort on having a robust UI. THe
important thing is to recognize when the situation arises and give a _clear_
feedback about the with access to the stuff that really matters in that
situation (ie: why don't you have any cores? was there an error? how to i add a
core?) ... even if that UI is incredibly simplified.
In my patch, i was trying to maintain the nav links in the left, so new users
would at least have a taste for what features the UI offers once cores are
added (and so we could have a place to incorporate SOLR-3635) ... but that's
certainly not necessary.
I think the way to go for now is a new, simple, screen w/o any assumptions
about anything else that says "You don't have any cores, here's the form to add
a core, and BTW here are some known init failures from other cores that might
explain why you don't have any cores."
> web UI reports and error if CoreAdminHandler says there are no SolrCores
> ------------------------------------------------------------------------
>
> Key: SOLR-3633
> URL: https://issues.apache.org/jira/browse/SOLR-3633
> Project: Solr
> Issue Type: Bug
> Components: web gui
> Affects Versions: 4.0-ALPHA
> Reporter: Hoss Man
> Assignee: Stefan Matheis (steffkes)
> Fix For: 4.0
>
> Attachments: SOLR-3633-message.patch, SOLR-3633.patch
>
>
> Spun off from SOLR-3591...
> * having no SolrCores is a valid situation
> * independent of what may happen in SOLR-3591, the web UI should cleanly deal
> with there being no SolrCores, and just hide/grey out any tabs that can't be
> supported w/o at least one core
> * even if there are no SolrCores the core admin features (ie: creating a new
> core) should be accessible in the UI
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
