[
https://issues.apache.org/jira/browse/SOLR-11508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273530#comment-16273530
]
Marc Morissette commented on SOLR-11508:
----------------------------------------
I've created this bug because a lot of documentation (including the
command-line help) indicates that SOLR_DATA_HOME is how you store your data
outside the installation. It's true but quite misleading because a lot of what
is needed to load that data remains in coreRootDirectory.
Core.properties and the conf directory is not just config but metadata. If you
delete a core's directory, you would expect the metadata to follow. If you
download a new version of Solr and point it to your solr.data.home, you would
expect Solr to be able to load your cores without a sweat. Cores are databases
and their individual configuration should lie with them, not with the server
(except for configsets).
Now, I understand why this makes less sense to Solr veterans who have known
Solr for a long time but please understand how inintuitive this feels to
SolrCloud and less experimented users.
My patch does not add or remove any feature. You can still configure different
values for SOLR_DATA_HOME and coreRootDirectory. I've simply changed the
defaults to something I consider more intuitive (God knows Solr could use a
little more of that).
Yes, changing the default could break some installations (those that have
defined SOLR_DATA_HOME but not coreRootDirectory) but that is why I've added
the release note. I feel this is acceptable as long as it makes Solr easier to
use. Believe me, I'm not the first one to be tripped up by this issue.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
