[
https://issues.apache.org/jira/browse/SOLR-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752921#action_12752921
]
Noble Paul commented on SOLR-1396:
----------------------------------
it is not enough to have simple configuration. we need standardized parsing
also. I have modified SolrConfig in such a way that we must not need to write
any xml parsing for new components as long as we stick to the standard syntax
(SOLR-1198). Going forward SolrConfig implementation should be pluggable and
be xml independent, we should have a simplified interface for SolrConfig so
that users can read it from anywhere (xml, zookeeper,db etct etc)
> standardize the updateprocessorchain syntax
> -------------------------------------------
>
> Key: SOLR-1396
> URL: https://issues.apache.org/jira/browse/SOLR-1396
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Fix For: 1.4
>
>
> 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.
