[
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729905#comment-13729905
]
Hoss Man commented on SOLR-5103:
--------------------------------
bq. a self--contained archive of a plugin that can be easily installed (even
from the UI!) and configured programmatically.
bq. +1 for this! Keep the configuration w/ the plugin and don't require any
central place to "wire it up".
can someone give me a practical/hypothetical example of what this would look
like to someone setting up a solr instance?
For all the examples i can think of, this doens't really make sens to me --
specifically: all of the existing plugins you can find in "solr/contrib" ...
are we expecting users to JAR up their own "copy" of DIH with it's config
inside of it's jar? are we expecting people who want to use the langid update
processor to re-jar it with some bit of config snippet that tells it what
fields to populate and what langauge to look for? ... and then what? they drop
that jar into some directory, and it still does nothing until they
programatically use some API to say which of their (possibly may) update
processor chains they want it to be a part of, and where in the chain it should
execute?
> Plugin Improvements
> -------------------
>
> Key: SOLR-5103
> URL: https://issues.apache.org/jira/browse/SOLR-5103
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Fix For: 5.0
>
>
> I think for 5.0, we should make it easier to add plugins by defining a plugin
> package, ala a Hadoop Job jar, which is a self--contained archive of a plugin
> that can be easily installed (even from the UI!) and configured
> programmatically.
--
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: [email protected]
For additional commands, e-mail: [email protected]
