lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Commented: (SOLR-1449) solrconfig.xml syntax to add classpath elements from outside of instanceDir
Date Thu, 01 Oct 2009 16:43:23 GMT


Hoss Man commented on SOLR-1449:

Noble: if you have any specific suggested improvements for the patch that you think will make
eventual work on SOLR-919 easier, then i'm all ears -- but i'd rather not try to code something
in anticipation of a future feature that doesn't even have a stub patch or fleshed out design

Even if we don't make any of the changes suggested in this issue, some very complicated questions
are going to have to be answered in SOLR-919 -- like: should two cores sharing a SolrConfig
object and an instanceDir (but with different data dir propertes) share the same resourceloader/classloader,
or should they have unique classloaders containing different copies of the same jars from
./lib.   Those types of questions aren't things we should be attempting to answer in this
issue -- but they will ultimately need to be addressed in SOLR-919, and they will need to
be addressed regardless of what we decide to do here.

This patch doesn't change any of the internal public APIs, it just adds support for some new
syntax in the config file, so if SolrConfig.initLibs needs to be refactored later to support
SOLR-919 that will be totally fine.

> solrconfig.xml syntax to add classpath elements from outside of instanceDir
> ---------------------------------------------------------------------------
>                 Key: SOLR-1449
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 1.4
>         Attachments: SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch,
SOLR-1449.patch, SOLR-1449.patch, SOLR-1449.patch
> the idea has been discussed numerous times that it would be nice if there was a way to
configure a core to load plugins from specific jars (or "classes" style directories) by path
 w/o needing to copy them to the "./lib" dir in the instanceDir.
> The current workaround is "symlinks" but that doesn't really help the situation of the
Solr Release artifacts, where we wind up making numerous copies of jars to support multiple
example directories (you can't have reliable symlinks in zip files)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message