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

Shawn Heisey commented on SOLR-4268:
------------------------------------

Does this issue still make sense?  I think it probably does.

This comment is part of an effort to close old issues that I have reported.  
Search tag: elyograg2013springclean

                
> Admin UI - button to unload transient core without removing from solr.xml
> -------------------------------------------------------------------------
>
>                 Key: SOLR-4268
>                 URL: https://issues.apache.org/jira/browse/SOLR-4268
>             Project: Solr
>          Issue Type: Improvement
>          Components: web gui
>    Affects Versions: 4.0
>            Reporter: Shawn Heisey
>             Fix For: 4.3
>
>
> The core "unload" button in the UI currently will completely remove a core 
> from solr.xml.  With the implentation of transient cores, there should be a 
> way to ask Solr to unload a core without removing it entirely.
> This leads into a discussion about terminology.  UNLOAD isn't a good 
> single-word description for what it does.  A case could be made for having 
> REMOVE and DELETE actions for CoreAdmin, with confirmation prompts if you 
> click on those buttons in the UI.  DELETE could simply be an option on REMOVE 
> - which I think you can actually currently do with UNLOAD.
> Another idea, not sure if it needs its own issue or is part of this one: If a 
> core is mentioned in solr.xml but not actually loaded, it would be very cool 
> if it were listed, but with a different background color to indicate the 
> non-loaded state.

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