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

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

[~jkrupan] 
A lot of your suggestions are not realy in the scope of this ticket and should 
be addressed separately

bq. Consider supporting both a single parameter with a csv list as well as 
multiple parameters each with a single value. I prefer having the choice.

I think having choices is not really good if it doesn't offer anything better.

bq.Consider a single-processor parameter with the option to specify the 
parameters for that processor. 

This is just too complex to handle with the flat http parameter structure. 
Again beyond the scope

URPs are really powerful but they are a bit hard to configure and use. I wish 
to make it easier and more widely used. That is the  objective of this ticket 

> 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: 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 
> * 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