[
https://issues.apache.org/jira/browse/SOLR-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423268#comment-13423268
]
Stefan Matheis (steffkes) edited comment on SOLR-3633 at 7/26/12 5:37 PM:
--------------------------------------------------------------------------
Doh, you're right - i missed SOLR-3677 :/ ignore my one, it does more or less
exactly the same then yours.
What i don't know .. 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? or is it only kind of "mapping"
/ changing a listener or whatever?
Because, if we have all the global ui-options really global (available if we
have no cores available) it should be a small(er) chance to type of initial
state for the ui -- in that case we "only" have to avoid the step where the ui
generates the list containing all loaded cores?
was (Author: steffkes):
Doh, you're right - i missed SOLR-3677 -.- ignore my one, it does more or
less exactly the same then yours.
What i don't know .. 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? or is it only kind of "mapping"
/ changing a listener or whatever?
Because, if we have all the global ui-options really global (available if we
have no cores available) it should be a small(er) chance to type of initial
state for the ui -- in that case we "only" have to avoid the step where the ui
generates the list containing all loaded 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]
