[
https://issues.apache.org/jira/browse/SOLR-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998091#comment-12998091
]
Hoss Man commented on SOLR-2370:
--------------------------------
I'm sort of on board this ... peronally i think UpdateProcessors are a
complicated enough beast that if you are configuring them you *reallY* need to
configure the whole chain -- but assuming i'm in the minority there, the part i
don't understand is the value add in the 'customer made chain will be only the
"center" part' and {{reset="true"}} pieces ... that seems overly complicated.
The pattern (ultimately) implemented with search components was that:
* If first-components was specified, it came before the default list.
* If last-components was specified, it came after the default list, but before
debug.
* If a full components list was specified (instead of first/last lists) it
overrode the entire default list.
the same pattern seems like it would make perfect sense here - substituting
RunUpdateProcessorFactory for DebugComponent. If you specify your own complete
chain, then you override the complete chain. If you specify a list of
first-components they come before all the defualt stuff. if you specify
last-components they come after default stuff, but RunUpdateProcessorFactory is
still used at the end.
what am i missing that necessitates this idea of replacing the "center" part of
the chain being the default?
(maybe i'm just missing the point of the examples ... it owuld help to know
what the hypothetical default chain is in these scenerios, and then what the
final resulting chain would be in each instance)
> 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]
