[
https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259410#comment-14259410
]
Alexandre Rafalovitch commented on SOLR-6892:
---------------------------------------------
This use case does not feel strong enough to be *Major*. Are there specific
business use-cases that really cannot be solved with pre-defined chains?
Also, a lot of URPs take parameters. The proposal above does not seem to allow
that. And then what about DistributedUpdateProcessor and that the chains allow
to specify items both before and after it.
Also consider troubleshooting. It needs to be very clear what applied to the
content as it came in. How would one find out if a chain was applied
incorrectly.
Finally, what are "built update processors"? "Built-in?" So far, vast majority
of them are built-in, as in shipped with Solr. And have their own class names.
Do you means some standard *chains* could be pre-built and named? Do you have a
good example? I would say these arguments apply a lot more to the analyzer
chains (I'd love to see those built-in), but I am not sure about URPs.
> Make update processors toplevel components
> -------------------------------------------
>
> Key: SOLR-6892
> URL: https://issues.apache.org/jira/browse/SOLR-6892
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> The current update processor chain is rather cumbersome and we should be able
> to use the updateprocessors without a chain.
> The scope of this ticket is
> * <updateProcessor> tag becomes a toplevel tag and it will be equivalent to
> the <processor> tag inside <updateRequestProcessorChain> . The only
> difference is that it should require a {{name}} attribute
> * Any update request will be able to pass a param {{processor=a,b,c}} ,
> where a,b,c are names of update processors. A just in time chain will be
> created with those update processors
> * Some in built update processors (wherever possible) will be predefined with
> standard names and can be directly used in requests
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
