lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (SOLR-4653) Solr configuration should log inaccessible/ non-existent relative paths <lib dir="...">
Date Tue, 02 Apr 2013 13:09:16 GMT


Dawid Weiss commented on SOLR-4653:

Thanks for clarification, Hoss. What you say makes sense but the common practice seems to
be that:
* people modify the example's configuration files and overwrite them just because all the
paths are relative from those directories and pointing at contribs,
* when you want to create an isolate configuration and pass it to somebody to, say, run with
-Dsolr.solr.home it's hard because you need to know absolute installation paths or make the
user install that configuration in an exact folder under solr's unpacked structure. If they
change anything -- boom, things don't work and nobody knows what's going on.

I think the middle ground here is to at least log a warning when a fileset is empty (and provide
the basedir against which it was resolved). This looks suspicious and provides enough information
to recover from the problem.
> Solr configuration should log inaccessible/ non-existent relative paths <lib dir="...">
> ---------------------------------------------------------------------------------------
>                 Key: SOLR-4653
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message