[
https://issues.apache.org/jira/browse/SOLR-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13672673#comment-13672673
]
Aaron Greenspan commented on SOLR-3633:
---------------------------------------
As a new Solr user (4.3.0) I thought I'd remove the example core and create my
own. Both of those things turned out to be bad ideas. First, removing the core
caused the entire Web UI to irreversibly crash, which I solved just by
re-expanding the tarball. (Not a very elegant solution.)
Then, trying to create a new core one I had the example one back led to this
issue... https://issues.apache.org/jira/browse/SOLR-4461
The web UI looks nice, but to a novice it's basically unusable I'm sad to say.
> web UI reports an 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.4
>
> Attachments: SOLR-3633.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
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]
