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

Varun Thacker commented on SOLR-12068:
--------------------------------------

Thanks Amrit!

Uni-Directional : It's mandatory define the update processor chain on the target

Bi-Directional  : It's mandatory to define it on both source and target.

So removing this from the source in the uni-directional use-case will reduce 
3-4 lines of copy pasting but the user might look at it as an inconsistency.

I know it will work without it so the changes are correct hence I'm +0 for the 
change :)

 

> Minor documentation correction in cdcr-config.html
> --------------------------------------------------
>
>                 Key: SOLR-12068
>                 URL: https://issues.apache.org/jira/browse/SOLR-12068
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: CDCR, documentation
>    Affects Versions: 7.2
>            Reporter: Amrit Sarkar
>            Priority: Major
>             Fix For: 7.3, master (8.0)
>
>         Attachments: SOLR-12068.patch
>
>
> In sample source configuration for unidirectional approach in 
> cdcr-config.html, the following are optional and not necessary at all, hence 
> they should be emitted:
> {code}
> <updateRequestProcessorChain name="cdcr-processor-chain">
>   <processor class="solr.CdcrUpdateProcessorFactory"/>
>   <processor class="solr.RunUpdateProcessorFactory"/>
> </updateRequestProcessorChain>
> <requestHandler name="/update" class="solr.UpdateRequestHandler">
>   <lst name="defaults">
>     <str name="update.chain">cdcr-processor-chain</str>
>   </lst>
> </requestHandler>
> {code}
>   



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to