[
https://issues.apache.org/jira/browse/SOLR-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299518#comment-16299518
]
Michael Dürr commented on SOLR-11783:
-------------------------------------
Hi Erick,
thanks for your quick answering!
I don't think it is related to SOLR-11503 as the problem occurs in standalone
mode (i.e. not solr cloud).
It is very simple to reproduce the problem:
1. Go to <install_dir>/solr-7.1.0/solr/
2. Start techproducts example (./bin/solr -e techproducts)
3. Rename core (e.g. via solr UI or core admin api)
4. Check persistence (cat
example/techproducts/solr/techproducts/core.properties)
The core.properties file still holds the old core name (name=techproducts)
Performing the same steps with solr 6.3.0 works as expected, i.e. the
core.properties file holds the new core name.
> Rename core in solr standalone mode is not persisted
> ----------------------------------------------------
>
> Key: SOLR-11783
> URL: https://issues.apache.org/jira/browse/SOLR-11783
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server
> Affects Versions: 7.1
> Reporter: Michael Dürr
>
> After I upgraded from solr 6.3.0 to 7.1.0 I recognized that the RENAME admin
> command does not persist the new core name to the core.properties file.
> I'm not very familiar with the solr internals, but it seems like the
> {quote}CorePropertiesLocator.buildCoreProperties(CoreDescriptor cd){quote}
> method uses an invalid core descriptor to initialize the core properties that
> get written to the core properties file.
> Best regards,
> Michael
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
