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

Noble Paul commented on SOLR-1449:
----------------------------------

Let us get the facts. We may be barking up the wrong tree.

we have a 116MB distribution out of which the solr.war + single+multicore 
example is around 4MB .  Most of the users need this 4MB only (99% of the users 
do not need clustering + solr cell ). If we implement this issue we may cut 
down the size of the distro by around 20 MB (by eliminating duplication of tika 
jars).  What we should have is a lighter version (solr.war + example solr home 
. <4MB and a full version. 

I am sure most of the users will be happy with the minimal solr. The rest of 
them will happily download the whole thing however big it is.

This is not to say that we don't need to reduce the size of the distro. But 
adding complexity just for this is not really required. Just adding a .sh and 
.bat file to the tika example we can add jars from external path.

> 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
>             Fix For: 1.4
>
>         Attachments: 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.

Reply via email to