[
https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048661#comment-16048661
]
Noble Paul commented on SOLR-9565:
----------------------------------
bq.Instead of the magic -UpdateProcessorFactory suffix magic, can we perhaps
let all URPs be named SPIs like
Going forward, people will write their own URPs and how do you add these names
bq.Why continue inventing dot-separated config options for complex stuff like
this when we are moving towards JSON elsewhere?
I like json , but using a full json in request parameter is a big problem.
Users have to be careful about how to escape each character. Normal tools such
as postman support typing json in payload , but not in parameters
Until we come up with a better format we can use the dot separated syntax.
Whatever format we come up with has to be well thought out and should be a
common syntax for all, no just URPs
> 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]
