lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noble Paul (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SOLR-1396) standardize the updateprocessorchain syntax
Date Mon, 21 Sep 2009 06:00:18 GMT

     [ https://issues.apache.org/jira/browse/SOLR-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Noble Paul resolved SOLR-1396.
------------------------------

    Resolution: Won't Fix

with SOLR-1326 this kind of syntax is now standard for any type of plugin . so no changes
required

> standardize the updateprocessorchain syntax
> -------------------------------------------
>
>                 Key: SOLR-1396
>                 URL: https://issues.apache.org/jira/browse/SOLR-1396
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.3
>            Reporter: Noble Paul
>             Fix For: 1.5
>
>
> updateprocessorChain follows a non-standard syntax in solr . Usually, all the components
are initialized as top level components and they are assembled and used using a NamedList
syntax .for example search components.
> I propose to change it as follows
> {code:xml}
>  <updateRequestProcessorChain name="custom" class="solr.UpdateRequestProcessorChain">

>   <arr name="chain">
>       <str>custom</str>
>       <str>runUpdate</str>
>       <str>log</str>
>   </arr>
> </updateRequestProcessorChain>
> <updateProcessor name="custom" class="solr.CustomUpdateRequestProcessorFactory" >
>    <lst name="name">
>      <str name="n1">x1</str>
>      <str name="n2">x2</str>
>    </lst>
> </updateProcessor>                                    
> <updateProcessor name="runUpdate" class="solr.RunUpdateProcessorFactory" />   
                
> <updateProcessor name="log" class="solr.LogUpdateProcessorFactory" />   
> {code}
> The wiki documentation says this was supposed to be reviewed. If possible we should clean
it up in 1.4 itself. We can support the old syntax too

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message