[
https://issues.apache.org/jira/browse/SOLR-11783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301827#comment-16301827
]
Shawn Heisey commented on SOLR-11783:
-------------------------------------
I haven't been able to locate the problem, but I did encounter some odd
behavior. I did the recreate as outlined above, renaming the techproducts core
to "foo". Then I stopped Solr and started it back up with the bin\solr command
used by the "-e" option. Because core.properties hadn't been updated, the core
name was back to techproducts, as the issue describes.
Then I tried to change the core name again to "foo" but it told me "New name
must be different from the current one" ... which is really really odd,
particularly because Solr was restarted and the core was NOT named foo.
> 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
> Assignee: Erick Erickson
>
> 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]
