[
https://issues.apache.org/jira/browse/SOLR-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729972#comment-13729972
]
Hoss Man commented on SOLR-5103:
--------------------------------
bq. Small stuff shouldn't need any configuration... for instance a custom
QParser should just be able to work if it's in the classpath.
Ok, so something like a QParserPlugin could *optionally* register itself using
a "default" name hardcoded in it's code (similar to how SolrCore auto-wires the
"default" QParsers that come with solr-core out of hte box) ... but how would
that work if multiple plugins try to use the same name? (in solr-core we can
ensure that doesn't happen, and we don't register something with the same name
as a qparser explicitly registered via users configuration) Not to mention
you'd still need to support a method of explicitly registering QParserPlugins
since it might support init params that you want to specify (none of hte out of
the box QParsers do, but it's possible, and we shouldn't take that
customization away)
QParsers really seem like the "special case" not the common case as far as
plugins go and this sort of hypothetical "automatic loading & registration" ...
FieldTypes, Analysis factories, search components, request handlers, ... these
are all things i'm hard pressed to imagine being useul w/o some sort of
explicit "this is how i want to use it" type information from the person
admining the solr instance.
> 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]
