[
https://issues.apache.org/jira/browse/SOLR-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936881#comment-16936881
]
David Smiley commented on SOLR-13035:
-------------------------------------
I'd like to point out here that the Solr 8 docker image worked around this
issue by declaring solr's home to be in /var/solr/data along with some
initialization scripts that populate this with a copy of solr.xml and zoo.cfg
if the dir is empty.
https://github.com/docker-solr/docker-solr/blob/master/scripts/init-var-solr
I'm not sure where that leaves this issue... but it's certainly less important
now.
> Utilize solr.data.home / solrDataHome in solr.xml to set all writable files
> in single directory
> -----------------------------------------------------------------------------------------------
>
> Key: SOLR-13035
> URL: https://issues.apache.org/jira/browse/SOLR-13035
> Project: Solr
> Issue Type: Improvement
> Reporter: Amrit Sarkar
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Attachments: SOLR-13035.patch, SOLR-13035.patch, SOLR-13035.patch,
> SOLR-13035.patch, SOLR-13035.patch, SOLR-13035.patch,
> image-2019-08-28-23-57-39-826.png
>
>
> {{solr.data.home}} system property or {{solrDataHome}} in _solr.xml_ is
> already available as per SOLR-6671.
> The writable content in Solr are index files, core properties, and ZK data if
> embedded zookeeper is started in SolrCloud mode. It would be great if all
> writable content can come under the same directory to have separate READ-ONLY
> and WRITE-ONLY directories.
> It can then also solve official docker Solr image issues:
> https://github.com/docker-solr/docker-solr/issues/74
> https://github.com/docker-solr/docker-solr/issues/133
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
