[ https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049126#comment-16049126 ]
Jan Høydahl commented on SOLR-9565: ----------------------------------- You can already call Config API with {{add-updateprocessor}}, see http://lucene.apache.org/solr/guide/6_6/config-api.html#ConfigAPI-Whatabout_updateRequestProcessorChain_ and then use the name you selected in {{&processor=myName}}, so perhaps this is good enough even if it requires two steps? About making all URPs available implicitly I think that SPI can do much of the heavy-lifting here and then the {{add-updateprocessor}} can accept {{"id":"urp-spi-name"}} as alternative to {{"class":"solr.MyURPFactory"}} > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org