[
https://issues.apache.org/jira/browse/SOLR-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125641#comment-13125641
]
Jan Høydahl commented on SOLR-2823:
-----------------------------------
Sub chains could solve the exact example, but that was just for showing the
principle. I think (optinally) named processors are a more direct solution.
Think of the named processors as processor configs, not necessarily 1:1 with
Java objects. When instansiating the "crawl" chain we'd simply fetch the config
from the referenced element instead of inline. It may still have a distinct
"solr.LanguageIdentifierUpdateProcessorFactory" class instance from the "cms"
pipeline.
Sub chains may also come in handy for some situations, but that could be
handled separately later, if needed.
> Re-use of UpdateProcessor configurations in multiple UpdateChains
> -----------------------------------------------------------------
>
> Key: SOLR-2823
> URL: https://issues.apache.org/jira/browse/SOLR-2823
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Jan Høydahl
> Priority: Minor
>
> When dealing with multiple UpdateChains and Processors, you frequently need
> to re-use configuration. Two chains may be equal except for one config
> setting in one <processor>.
> I propose to allow named processor configs, which can be referenced by name
> in the chains.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
