Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
4.10, 5.5, 6.6
-
None
-
None
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
Attachments
Issue Links
- is superceded by
-
SOLR-14783 Remove DIH from 9.0
- Closed
- relates to
-
SOLR-1970 need to customize location of dataimport.properties
- Closed