[
https://issues.apache.org/jira/browse/SOLR-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729424#comment-13729424
]
Daniel Collins commented on SOLR-5102:
--------------------------------------
Maybe the more important question is "what does solr.home mean and what should
it contain?" If using Solr Cloud, then solr.home is just solr.xml, zoo.cfg,
and directories containing core.properties files. That is purely "data" and
"configuration", so I'd agree with Noble Paul, I wouldn't want that to live
alongside JARs or "code". I know the distinctions as a web-app are not as
clear, but treating Solr like an application (which we do), we like to keep a
nice distinction between code and data and I think I would object to something
that forced it all to live in one area.
For upgrades (assuming we migrate away from web-apps at some point), again it
would be nice to keep the "custom" stuff, i.e. solr.xml, zoo.cfg and all my
core configuration/data away from solr "code", so I could migrate between Solr
versions for an upgrade path more cleanly.
> Simplify Solr Home
> ------------------
>
> Key: SOLR-5102
> URL: https://issues.apache.org/jira/browse/SOLR-5102
> Project: Solr
> Issue Type: Bug
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Fix For: 5.0
>
>
> I think for 5.0, we should re-think some of the variations we support around
> things like Solr Home, etc. We have a fair bit of code, I suspect that could
> just go away if make it easier by assuming there is a single solr home where
> everything lives. The notion of making that stuff configurable has outlived
> its usefulness
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
