[
https://issues.apache.org/jira/browse/SOLR-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998236#comment-12998236
]
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
DistributedUpdateProcessor
CustomUpdateProcessor
CustomUpdateProcessor
LogUpdateProcessor
RunUpdateProcessor
Thus in my head it makes most sense to insert user chains in the middle. A more
explicit way to do that could be
{code}
<updateRequestProcessorChain name="mychain">
<middle-processors>
<processor class="my.nice.DoSomethingProcessor"/>
<processor class="my.nice.DoAnotherThingProcessor"/>
</middle-processors>
</updateRequestProcessorChain>
{code}
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: https://issues.apache.org/jira/browse/SOLR-2370
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
