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

Jan Høydahl commented on SOLR-9565:
-----------------------------------

bq. But how do we do it in Solr? There is no such plugin registration mechanism
SPI is a Java feature, and I guess we could do the same as Analysis has done 
with {{org.apache.lucene.analysis.util.AnalysisSPILoader}} i.e. 
{{URProcessorSPILoader}}?

On a side note I would also very much like for Solr's schema to switch to 
configuring tokenizers, filters and charfilters using their SPI name instead of 
full class name, e.g. {{<filter name="synonym">}} instead of {{<filter 
class=solr.SynonymFilterFactory">}}, see also discussion in 
[SOLR-5287|https://issues.apache.org/jira/browse/SOLR-5287?focusedCommentId=13782255&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13782255]

bq. I would rather want to create a more generic json payload to be created 
using the params API and reference it in a given request.
If the whole point is that it should be possible to issue a one-off query with 
URP processing without prior configuration, then all needs to go in the same 
request.

> 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
>
> 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]

Reply via email to