lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] Commented: (SOLR-2370) Let some UpdateProcessors be default without explicitly configuring them
Date Wed, 23 Feb 2011 08:36:38 GMT


Jan Høydahl commented on SOLR-2370:

I was assuming that the DistributedUpdateHandler would always want to run first, and then
the rest of the processing could happen per shard. That way you get somewhat load balanced
processing, compared to running the whole chain before distributing. Thus you have


Thus in my head it makes most sense to insert user chains in the middle. A more explicit way
to do that could be
<updateRequestProcessorChain name="mychain">
    <processor class="my.nice.DoSomethingProcessor"/>
    <processor class="my.nice.DoAnotherThingProcessor"/>
and let the existing syntax define the whole chain as today. We then only need to find a way
to mark the "middle" of the default chain.

> Let some UpdateProcessors be default without explicitly configuring them
> ------------------------------------------------------------------------
>                 Key: SOLR-2370
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>            Reporter: Jan Høydahl
>              Labels: UpdateProcessor, UpdateProcessorChain
> Problem:
> Today the user needs to make sure that crucial UpdateProcessors like the Log- and Run
UpdateProcessors are present when creating a new UpdateRequestProcessorChain. This is error
prone, and when introducing a new core UpdateProcessor, like in SOLR-2358, all existing users
need to insert the changes into all their pipelines.
> A customer made pipeline should not need to care about distributed indexing, logging
or anything else, and should be as slim as possible.

This message is automatically generated by JIRA.
For more information on JIRA, see:


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

View raw message