[
https://issues.apache.org/jira/browse/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618973#comment-13618973
]
Hoss Man commented on SOLR-4653:
--------------------------------
The original intent was:
* If users want solr to be very strict and fail loudly if your any of your
plugin jars can't be found, then you should know what plugin jars you car about
and use an explicit "path" option for each of them.
* for the purposes of the example configs, we wanted something less strict so
that (combined with the lazy load option on plugins) the example configs could
refer to contrib jars and the bulk of the example configs would still work even
if you didn't build any of those contribs, or moved/copied the example configs
-- if you do either of those things, and then try to use any of those lazy
loaded plugins, the lazy loading feature will give you a loud error.
At this point, i don't have any strong opinions about changing any of this
behavior to be a hard failure if the "dir" doesn't exist, or if the regex
doesn't match anything -- the way the current build system works "ant example"
already builds all of the contribs anyway regardless of wether you care about
them, so the key concern is really just what would happen when people move/copy
the example configs.
I suspect that if we change this to cause a hard failure the number of users
who might be confused/anoyed about why they are getting those errors when they
move/copy the example configs (and need to remove those <lib/> directives) will
probably be roughly the same as the number of users who (with the existing
configs) are confused by the lazy loading errors they get trying to use DIH, or
solr-cell, or /browse after they move/copy the configs today and have to go
update where the <lib/> directives point at.
> Solr configuration should log inaccessible/ non-existent relative paths <lib
> dir="...">
> ---------------------------------------------------------------------------------------
>
> Key: SOLR-4653
> URL: https://issues.apache.org/jira/browse/SOLR-4653
> Project: Solr
> Issue Type: Bug
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
>
> Currently the dir path is resolved relative to core's instanceDir but if you
> don't know it nothing happens (no warning, no nothing). This is very
> frustrating.
--
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: [email protected]
For additional commands, e-mail: [email protected]
