lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <>
Subject [jira] [Updated] (SOLR-6892) Make it possible to define update request processors as toplevel components
Date Sun, 28 Dec 2014 16:29:13 GMT


Noble Paul updated SOLR-6892:
    Issue Type: Improvement  (was: Bug)

> Make it possible to define update request processors as toplevel components 
> ----------------------------------------------------------------------------
>                 Key: SOLR-6892
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message