[
https://issues.apache.org/jira/browse/SOLR-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758409#action_12758409
]
Shalin Shekhar Mangar commented on SOLR-1449:
---------------------------------------------
bq. For the same reason we have an example at all I guess - a better
out-of-the-box experience.
I agree with that goal. It's just that having a regex based class loading from
externally located jars, although cool, seems an overly fancy way to solve this
particular problem.
bq. It would be nice if we could do database import from the same example
server... but I think JDBC driver issues (and the necessity to have a database
to connect to?) make this tougher.
The database and the driver jar is checked in. The only issue I guess is that
our example is a single-core one and the DIH examples have db, rss and mail
each of which requires its own schema.
The main problem is the mail DIH example. It uses Tika for indexing email
attachments and therefore copies all its dependencies. I'm not sure if that is
necessary. We can have an option to disable that and document the attachment
support in the wiki only. I'm guessing that very few users will actually need
to look at that example.
The other thing that we can do is to offer separate source and binary+example
downloads.
> 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
>
>
> 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.
