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

Aaron Greenspan commented on SOLR-3633:
---------------------------------------

Mark,

Perhaps it doesn't crash in that it doesn't throw a segmentation fault, but it 
does throw a Java exception and then stops working, which for a novice user 
like me means that there is no way to go back and add a core (since the only 
way I'd know how to do it is through the web UI)--the only way to fix it. And 
even if there was such a way to add a core, I'd run into issue 4461, and not be 
able to anyway.

Aaron
                
> 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]

Reply via email to