lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-4653) Solr configuration should log inaccessible/ non-existent relative paths <lib dir="...">
Date Mon, 01 Apr 2013 18:25:16 GMT

    [ https://issues.apache.org/jira/browse/SOLR-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619009#comment-13619009
] 

Yonik Seeley commented on SOLR-4653:
------------------------------------

bq. 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 [...]

Right.  This is really more a change in behavior than a bug fix, and it seems like we should
be comprehensive and also deal with the reasons why it was added in the first place (i.e.
we need to figure out what to do with the lazy loaded plugins like solr-cell).  Docs like
the README under example, and http://wiki.apache.org/solr/ExtractingRequestHandler would also
need to change.

Changing to a hard fail has back compat issues too.  We have often recommended copying the
"example" directory as a starting point, and most of those will be pointing to directores
that don't exist.

On balance it feels like not failing hard (i.e. keeping the current behavior, but adding logging)
is the best middle ground right now.  If one does get a class-not-found exception, we'll have
the better logging to help track it down.

                
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message