[
https://issues.apache.org/jira/browse/SOLR-11402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jamie Jackson updated SOLR-11402:
---------------------------------
Description:
Currently, DIH drops the {{dataimport.properties}} file in the core directory
by default, but the data directory seems to be the logical choice.
* The core directory tends to be read-only.
* The data directory is the write area, and the {{dataimport.properties}} file
is tied to the index, rather than the core configurations.
Docker is a use case where the current behavior is glaringly problematic: The
core directory lives in the container layer, and any files that Solr writes
there disappear when the container is restarted (forcing a subsequent full
index). The data directory, on the other hand, is already persisted to a volume
(according to normal practice), so if it were the default location to write
{{dataimport.properties}}, it would behave as one would expect.
It's possible to work around this (using PropertyWriter, symlinks, or other
tricks), but this shouldn't be necessary.
* Downstream Solr Docker ticket:
https://github.com/docker-solr/docker-solr/issues/150
* SOLR-1970, in which others make the same argument
was:
Currently, DIH drops the {{dataimport.properties}} file in the cores directory
by default, but the data directory seems to be the logical choice.
* The core directory tends to be read-only.
* The data directory is the write area, and the {{dataimport.properties}} file
is tied to the index, rather than the core configurations.
Docker is a use case where the current behavior is glaringly problematic: The
cores directory lives in the container layer, and any files that Solr writes
there disappear when the container is restarted (forcing a subsequent full
index). The data directory, on the other hand, is already persisted to a volume
(according to normal practice), so if it were the default location to write
{{dataimport.properties}}, it would behave as one would expect.
It's possible to work around this (using PropertyWriter, symlinks, or other
tricks), but this shouldn't be necessary.
* Downstream Solr Docker ticket:
https://github.com/docker-solr/docker-solr/issues/150
* SOLR-1970, in which others make the same argument
> DataImportHandler dataimport.properties should write to data dir by default
> ---------------------------------------------------------------------------
>
> Key: SOLR-11402
> URL: https://issues.apache.org/jira/browse/SOLR-11402
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: contrib - DataImportHandler
> Affects Versions: 4.10, 5.5, 6.6
> Reporter: Jamie Jackson
> Priority: Minor
>
> Currently, DIH drops the {{dataimport.properties}} file in the core directory
> by default, but the data directory seems to be the logical choice.
> * The core directory tends to be read-only.
> * The data directory is the write area, and the {{dataimport.properties}}
> file is tied to the index, rather than the core configurations.
> Docker is a use case where the current behavior is glaringly problematic: The
> core directory lives in the container layer, and any files that Solr writes
> there disappear when the container is restarted (forcing a subsequent full
> index). The data directory, on the other hand, is already persisted to a
> volume (according to normal practice), so if it were the default location to
> write {{dataimport.properties}}, it would behave as one would expect.
> It's possible to work around this (using PropertyWriter, symlinks, or other
> tricks), but this shouldn't be necessary.
> * Downstream Solr Docker ticket:
> https://github.com/docker-solr/docker-solr/issues/150
> * SOLR-1970, in which others make the same argument
--
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
