[
https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16051806#comment-16051806
]
Jan Høydahl commented on SOLR-9565:
-----------------------------------
bq. What do you mean by hard coding? Nothing is hard coded
See code fragment in [my comment
above|https://issues.apache.org/jira/browse/SOLR-9565?focusedCommentId=16050191&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16050191].
Making {{UpdateRequestProcessorChain}} compile time dependent on a few select
URP plugins creates one way to implicitly register plugins made by committers
and no way at all to make 3rd party URP plugins implicitly available. That
makes some plugins "more alike" than others...
bq. BTW, are you aware of the fact that names of responseWriter, qparserPlugin,
valueSourceParser, transformerFactory and requestHandler are hard coded in
Solr. But, we also allow them to be configured with another name
I sure am. And I think we should change those as well to be auto discovered
instead of explicitly listed in a Java file. {{AnalysisSPILoader}} does a good
job with analysis plugins, and Solr could take advantage of that in allowing
short-name references to filters in {{<analysis>}} in schema. We can do the
same for all these others. Just drop your jar file into lib folder, start Solr
and start referring to the classes by well known name.
> Make every UpdateRequestProcessor available implicitly
> ------------------------------------------------------
>
> Key: SOLR-9565
> URL: https://issues.apache.org/jira/browse/SOLR-9565
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Attachments: SOLR-9565.patch
>
>
> Now that we can 'construct' the URP chains through request parameters, we
> should make all the URPs available automatically. The next challenge is to
> make them read the configuration from request parameters as well
> to access {{HTMLStripFieldUpdateProcessorFactory}} the parameter could be
> {{processor=HTMLStripField}} (The UpdateProcessorFactory part is
> automatically appended )
> The next step is to make the URPs accept request parameters instead of just
> configuration parameters e.g:
> {{processor=HTMLStripField&HTMLStripField.fieldName=<some-field>}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
