lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-1449) solrconfig.xml syntax to add classpath elements from outside of instanceDir
Date Mon, 05 Oct 2009 02:27:56 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Miller updated SOLR-1449:
------------------------------

    Attachment: SOLR-1449.patch

I haven't had a chance to do any testing yet, but just took some time reviewing the patch.

1. Should the change in clustering/example/conf/schema.xml be part of this patch?

Here is a no credit update to the patch that fixes a few small things:

2. example README formatting
3. Fix spelling in SolrResourceLoader.addToClassLaoder method
4. Fix liib spelling in build.xml

A couple thoughts:

5. Did you consider just extending URLClassLoader and opening up addUrl rather than replacing
the loader? Almost seems nicer - no biggie though.
6. What about solr.xml's sharedlib setting? Should it support the same syntax options as the
solrconfig lib setting ?

Hopefully I can do some testing too.

> solrconfig.xml syntax to add classpath elements from outside of instanceDir
> ---------------------------------------------------------------------------
>
>                 Key: SOLR-1449
>                 URL: https://issues.apache.org/jira/browse/SOLR-1449
>             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, 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.


Mime
View raw message