[
https://issues.apache.org/jira/browse/SOLR-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15180592#comment-15180592
]
Shawn Heisey commented on SOLR-6671:
------------------------------------
I really like this idea. It probably wouldn't work well for me without some
tweaking, but for a typical Solr user, it could be a lifesaver.
I use core.properties files like the following, so the instanceDir and dataDir
names do not include the "live" and "build" parts of the core names, which get
swapped when I do a full rebuild:
{noformat}
#Written by CorePropertiesLocator
#Mon Feb 01 23:57:50 UTC 2016
name=s0live
loadonStartup=false
dataDir=../../data/s0_1
transient=false
{noformat}
{noformat}
#Written by CorePropertiesLocator
#Mon Feb 01 23:57:50 UTC 2016
name=s0build
loadonStartup=false
dataDir=../../data/s0_0
transient=false
{noformat}
What determines the name of the dataDir? Is it the core name, or is the last
path component of the instanceDir? If it's the core name, that won't work for
me -- I would need it to be the last path component on instanceDir.
If the feature were set up so that I could have a core.properties file like
this that would do the right thing, it would be really nice:
{noformat}
name=s0live
dataDir=s0_1
{noformat}
> Introduce a solr.data.root as root dir for all data
> ---------------------------------------------------
>
> Key: SOLR-6671
> URL: https://issues.apache.org/jira/browse/SOLR-6671
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.10.1
> Reporter: Jan Høydahl
> Assignee: Shawn Heisey
> Fix For: 5.2, master
>
> Attachments: SOLR-6671.patch
>
>
> Many users prefer to deploy code, config and data on separate disk locations,
> so the default of placing the indexes under
> {{$\{solr.solr.home\}/$\{solr.core.name\}/data}} is not always wanted.
> In a multi-core/collection system, there is not much help in the
> {{solr.data.dir}} option, as it would set the {{dataDir}} to the same folder
> for all collections. One workaround, if you don't want to hardcode paths in
> your {{solrconfig.xml}}, is to specify the {{dataDir}} property in each
> {{solr.properties}} file.
> A more elegant solution would be to introduce a new Java-option
> {{solr.data.root}} which would be to data the same as {{solr.solr.home}} is
> for config. If set, all collections would default their {{dataDir}} as
> {{$\{solr.data.root\)/$\{solr.core.name\}/data}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]