[
https://issues.apache.org/jira/browse/SOLR-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422964#comment-13422964
]
Stefan Matheis (steffkes) commented on SOLR-3633:
-------------------------------------------------
Hoss, i'm sorry for the long delay
I guess i get the idea you're following, but i'm not sure if we are ready for
this yet. because almost all "global" actions are using core-specific urls to
fetch their information. not because i like to do it like that, just because
that's the only way to get this information.
Afaik the Cloud-Stuff is the only part which gets his data from
{{/solr/zookeeper}} -- Logging loads from {{/solr/collection1/admin/logging}},
Java Properties from {{/solr/collection1/admin/properties}} and Threads from
{{/solr/collection1/admin/threads}}
so, w/o having a least one core initialized .. already the dashboard will have
problems, because it actually uses {{/solr/collection1/admin/system}} :/
bq. If we can't make progress on this soon, then it would be best to commit a
simpler error check for no cores that hides all the navigation (much like hte
current "you need the /admin/ handler") with a clear message that there are no
cores
I would prefer this one (for now), even if i don't like to have it like this
(in general). Better to clearly state what's possible and what not .. as in
comparison have some "may or may not work - depending on .." state?
I'll attach an small and simple patch which also shows an warning screen but
with a specific message, for no cores being loaded
> 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.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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
