[
https://issues.apache.org/jira/browse/SOLR-6718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287937#comment-14287937
]
Shawn Heisey commented on SOLR-6718:
------------------------------------
No need to re-open, but I'd like to bring up a point for anyone that finds this
issue.
The coreRootDirectory defaults to the solr home if you don't specify it in
solr.xml.
If you are going to use a coreRootDirectory that's underneath the solr home,
you may be able to leave coreRootDirectory out of solr.xml entirely and still
get the functionality you want. As long as you don't have core.properties
files in any other location under the solr home besides the place you want Solr
to search, and there aren't thousands or millions of files/directories, it
won't present any problems to have Solr search the entire solr home.
> relative coreRootDirectory evaluated against CWD, not Solr Home
> ---------------------------------------------------------------
>
> Key: SOLR-6718
> URL: https://issues.apache.org/jira/browse/SOLR-6718
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.10
> Reporter: Hoss Man
> Assignee: Alan Woodward
> Priority: Blocker
> Fix For: 5.0
>
> Attachments: SOLR-6718.patch, SOLR-6718.patch, SOLR-6718.patch
>
>
> as reported by Andreas Hubold on solr-user...
> {noformat}
> I'd like to just set it to a subdirectory of solr home (a "cores" directory to
> avoid confusion with configsets and other directories). I tried
> <str name="coreRootDirectory">cores</str>
> but that's interpreted relative to the current working directory. Other paths
> such as sharedLib are interpreted relative to Solr Home and I had expected
> this here too.
> {noformat}
> This is definitely non-intuitive and we should try to fix it in 5.0 since it
> will represent a back-compat change for anyone already using a relative path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
