[ 
https://issues.apache.org/jira/browse/SOLR-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128286#comment-13128286
 ] 

Hoss Man commented on SOLR-2823:
--------------------------------


bq. 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.

To be clear: i wasn't arguing that the subchain syntax i suggested would be 1:1 
with java objects either, it could work exactly as you intend named processors 
to work (ie: pure syntactic sugar).  my suggestions was just that if we allow 
"subchain by reference" type configuration, it would achieve everything you 
describe using named processors (because you could have a sub-chain containing 
a single processor) _and_ it would handle the common case of chains that have a 
lot in common, but do some extra stuff at the beginning/end.

bq. Sub chains may also come in handy for some situations, but that could be 
handled separately later, if needed.

Eh .. i guess .. but it seems like it would be less total work to just do 
subchains and let people use chains of one processor to deal with the "reusing 
individual processor configs" usecase(s).

(FWIW: Don't let my comments stop/dissuade you, either way would be a huge 
improvement over what we've got now ... i just wanted to point out something 
that seemed like more bang for the buck)
                
> 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

Reply via email to