[ https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259567#comment-14259567 ]
Jack Krupansky commented on SOLR-6892: -------------------------------------- It might be instructive to look at how the search handler deals with search components and possibly consider rationalizing the two handlers so that there is a little more commonality in how lists of components/processors are specified. For example, consider a "first", "last", and full processor list. IOW, be able to specify a list of processors to apply before the solrconfig-specified list, after, or to completely replace the solrconfig-specified list of processors. > 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