[
https://issues.apache.org/jira/browse/SOLR-9565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050219#comment-16050219
]
Amrit Sarkar commented on SOLR-9565:
------------------------------------
just skimming;
Shouldn't support for {{processor=X}}, X in XURPFactory, continue? AtomicURP
can be invoked both via {{processor=atomic}}, simplified and
{{processor=Atomic}}, already supported. I saw complaints on StatelessScriptURP
where {{stateless}} is needless, {{processor=script}} can be handy there, along
with existing URPs shipped.
This will mean 3rd party URPs need not to do anything special out of order and
can use the prefix to invoke their respective processor.
> 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
> Attachments: SOLR-9565.patch
>
>
> 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
