[
https://issues.apache.org/jira/browse/SOLR-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675714#action_12675714
]
Michael Della Bitta commented on SOLR-1010:
-------------------------------------------
I'm a little unclear on why it would ever make sense to base any sort of
configuration path on where the container was invoked, because usage of a
container implies there might be other colocated apps and resulting conflicts
if other apps (which are likely Solr instances) worked in this way.
But even more so when I've made an obvious effort to override this behavior by
using something like JNDI. It seems to me that the type of user that's willing
to do the configuration work to set JNDI properties is the type of user that
wouldn't need to worry about the simplicity of having all paths work off the
invocation directory, and the configured solr.home should be considered the new
user.dir.
Maybe I'm missing the other argument because it doesn't apply to me somehow,
though.
> Relative instanceDir is evaluated relative to current working directory
> -----------------------------------------------------------------------
>
> Key: SOLR-1010
> URL: https://issues.apache.org/jira/browse/SOLR-1010
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.3
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 1.4
>
>
> If a relative instanceDir is provided in solr.xml, it should be evaluated
> relative to solr.home instead of the current working directory.
> I guess people work around this bug right now by using absolute paths for
> instanceDir.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
