[
https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049121#comment-16049121
]
David Smiley commented on SOLR-9565:
------------------------------------
Perhaps we simply need to accept that implicit registered URPs will sometimes
have limitations that aren't present when you configure the chain explicitly.
I think accepting that is better than a JSON based parameter for URPs -- I
don't think it's worth it. At least this is what I think.
BTW I suspect it will be uncommon for users to actually pass all these params
to Solr in an /update request. Perhaps for a quick prototype but for the
client to send them all each time under normal/production scenarios, I think I
would rather want to use initParams for the same reason initParams is available
for search. I'm a fan of parameters being defined Solr-side so that request to
Solr (be it for search and now for updates) have the essentials unique to the
request and not things that are constant. It's too bad there doesn't seem to
be an API to configure a chain; I have to modify solrconfig.xml. I often find
myself needing to edit the config files because there are Solr config API gaps,
so I often give up on the API altogether because I keep finding the gaps so
what's the point. Shrug; maybe that's just me?
+1 to the SPI registration mechanism.
> 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
