You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2017/12/20 16:18:00 UTC

[jira] [Commented] (SOLR-11783) Rename core in solr standalone mode is not persisted

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

Erick Erickson commented on SOLR-11783:
---------------------------------------

Michael:

This is perhaps SOLR-11503, which was in 7.2. Is there any chance you could give Solr 7.2 a try and see if the behavior persists?

If that doesn't fix the problem, please include an example of a core.properties file that is incorrect. Unfortunately "core name" is a bit ambiguous, there's coreNodeName, name, etc....

> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org