[
https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259384#comment-14259384
]
Erik Hatcher commented on SOLR-6892:
------------------------------------
While this does open up some potential custom power, I'm curious what use cases
you see with being able for the indexing client to specify the processors? It
is good that processors become their own first class component such that they
can be composed into update processor chains when (eventually) creating a chain
with API, but I can see using individual processors from the /update call being
a possible problem, such as not using the log processor and then not being able
to see what happened exactly.
> 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: [email protected]
For additional commands, e-mail: [email protected]
