[
https://issues.apache.org/jira/browse/SOLR-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271534#comment-16271534
]
ASF GitHub Bot commented on SOLR-11508:
---------------------------------------
Github user janhoy commented on the issue:
https://github.com/apache/lucene-solr/pull/278
Looks good to me
> core.properties should be stored $solr.data.home/$core.name
> -----------------------------------------------------------
>
> Key: SOLR-11508
> URL: https://issues.apache.org/jira/browse/SOLR-11508
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Marc Morissette
>
> Since Solr 7, it is possible to store Solr cores in separate disk locations
> using solr.data.home (see SOLR-6671). This is very useful where running Solr
> in Docker where data must be stored in a directory which is independent from
> the rest of the container.
> Unfortunately, while core data is stored in
> {{$\{solr.data.home}/$\{core.name}/index/...}}, core.properties is stored in
> {{$\{solr.solr.home}/$\{core.name}/core.properties}}.
> Reading SOLR-6671 comments, I think this was the expected behaviour but I
> don't think it is the correct one.
> In addition to being inelegant and counterintuitive, this has the drawback of
> stripping a core of its metadata and breaking core discovery when a Solr
> installation is redeployed, whether in Docker or not.
> core.properties is mostly metadata and although it contains some
> configuration, this configuration is specific to the core it accompanies. I
> believe it should be stored in solr.data.home, with the rest of the data it
> describes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
