[
https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16048786#comment-16048786
]
Jan Høydahl commented on SOLR-9565:
-----------------------------------
bq. Going forward, people will write their own URPs and how do you add these
names
This is also the case for analysis plugins. After you have installed a new 3rd
party token filter, you can address it in Lucene using its well-known SPI name
bq. using a full json in request parameter is a big problem
Yea, was thinking about json.facet, but as you say, that is typically sent in
request body, and for updates the request body is reserved for content... But
it's not strange to require clients to URL-encode a request parameter either,
they need to do that already, just that you need to do it more often with json.
The example from CloneFieldURP above was taken from the ref-guide and
illustrates what kind of config complexity we need to support, how do you do
that with simple dots? There is no point in supporting some config for some
URPs, and inventing a new parsing method for each seems sub optimal. The JSON
above could be converted to NamedList or whatever in a generalized way and
piggy-back on the existing config parser.
> 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]
