[
https://issues.apache.org/jira/browse/SOLR-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13771429#comment-13771429
]
Hoss Man commented on SOLR-5252:
--------------------------------
bq. Currently, core.properties is moved to core.properties.unloaded on an
UNLOAD command.
I may be wrong, but i vaguely remember a discussion about wether or not
core.properties should support an "enable=true|false" property, and the
decision ultimately being "no -- if people want to disable a core they should
delete / rename the properties file"
I suspect that is why you are seeing the rename.
I would suggest that this decision be re-thunk: it would be better if
enable=false in core.properties was supported and treated as if the
core.properties did not exist on startup, but would allow the file to be reused
(with enable=true automatically replaced with enable=true) on explicit CREATE
actions.
* would help fix this bug: the UNLOAD code could leave the file was left in
place, with enable=false added to it. subsequent CREATE command would parse
it, add/change any explicit params set on CREATE and write it back out.
* it would allow people an easy way to say "here is a core dir that i don't
want loaded by default on startup, but if it does get loaded via CREATE here
are some props to use unless the CREATE command overrides them.
> SolrCloud core UNLOAD + CREATE
> ------------------------------
>
> Key: SOLR-5252
> URL: https://issues.apache.org/jira/browse/SOLR-5252
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
>
> Unloading a core and then loading it again doesn't work.
--
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]
