lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <>
Subject [jira] [Commented] (SOLR-6892) Make update processors toplevel components
Date Sat, 27 Dec 2014 16:36:13 GMT


Alexandre Rafalovitch commented on SOLR-6892:

> Let's apply the transformers in the order they are specified and let the system take
care of the rest and avoid surprises

Actually, having a code hidden somewhere inside the system to do the non-trivial thing is
what will create surprises. Right now, the user can look at the XML file and step through
the cross-references to see what actually happened. Moving away into on-the-fly and case-by-case
will *increase* the surprises. So, the proposal and the reasoning are not quite aligned here.

Things like pre-defined names for standard components could decrease surprises. The rest of
the proposal does not. 

> Make update processors toplevel components 
> -------------------------------------------
>                 Key: SOLR-6892
>                 URL:
>             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

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

View raw message