[
https://issues.apache.org/jira/browse/SOLR-9575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15528104#comment-15528104
]
Erick Erickson commented on SOLR-9575:
--------------------------------------
+1 to Hoss' idea. I also would rather fail than do things under the covers.
If it addresses the basic concern I think it's a _much_ better idea than
creating the SOLR_HOME dir automagically.
> Initialize an empty solr-home
> -----------------------------
>
> Key: SOLR-9575
> URL: https://issues.apache.org/jira/browse/SOLR-9575
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
>
> The user may not want to use Solr's default solr-home dir location -- most
> likely to use a separate disk. If you do this, there are two main problems:
> * solr.xml & zoo.cfg aren't there
> * configsets aren't there
> Of course you could copy it manually but that's an extra step, and it's
> particularly annoying to add this step to a Docker setup. Docker is all the
> rage these days, and for good reason. If I mount a volume at
> /opt/solr/server/solr then it basically masks this part of the built-in Solr
> image (thus making configsets completely invisible) and points to some place
> that will be empty. Solr obviously complains. I could set the solr-home to
> some other path that I mount, but Solr would still complain about an empty
> solr-home -- no solr.xml
> If solr-home is empty, and if it's a dir other than the default solr-home,
> then I think the solr-home should be initialized with solr.xml and zoo.cfg
> copied from the default solr-home. I think configsets should be referenced
> from the default solr-home if there is no configsets dir in solr-home.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
