[ 
https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264905#comment-14264905
 ] 

Noble Paul commented on SOLR-6892:
----------------------------------

bq.I thought there were only two stages (pre- and post- 
DistributedUpdateProcessor
The "pre processor" mentioned above is not possible in the current URP chain. 
This is a new feature only 

bq.How do these three stages express themselves in the current URP chain

I'm not sure we should have the new features added to the old syntax and it 
does not fit very well there.

> Make it possible to define update request processors as toplevel components 
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-6892
>                 URL: https://issues.apache.org/jira/browse/SOLR-6892
>             Project: Solr
>          Issue Type: Improvement
>            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 
> * A new tag <updateProcessor>  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. The {{<updateProcessorChain>}} tag will 
> continue to exist and it should be possible to define <processor> inside as 
> well . It should also be possible to reference a named URP in a chain.
> * 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 URPs
> * Some in built update processors (wherever possible) will be predefined with 
> standard names and can be directly used in requests 
> * What happens when I say processor=a,b,c in a request? It will execute the 
> default chain after the just-in-time chain {{a->b->c}} . 
> * How to execute a different chain other than the default chain? the same old 
> mechanism of update.chain=x means that the chain  {{x}} will be applied after 
> {{a,b,c}}
> * How to avoid the default processor chain from being executed ? There will 
> be an implicit URP called {{STOP}} . send your request as 
> processor=a,b,c,STOP. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to