[ 
https://issues.apache.org/jira/browse/SOLR-11412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cassandra Targett updated SOLR-11412:
-------------------------------------
    Attachment: SOLR-11412.patch

I've attached an updated patch (SOLR-11412.patch) that has the CDCR page split 
into 4 new pages (for a total of 5 CDCR-related pages) along the lines I 
outlined the other day.

I took the liberty of updating the terminology a bit - there were frequent 
instances of "uni-directional scenario" and "bi-directional scenario", which 
made the word "scenario" seem over- and improperly used. I changed many of 
these to "updates" (with other sentence context changes to make it work). If 
this is also misleading, please let me know so we can fix before I commit.

I suspect the "CDCR Glossary" is, at this point, a bit redundant and out of 
place. I'd like to remove it, but for now left a comment that we should 
consider doing so in the future.

Otherwise, I think this is good to commit if others agree with the patch as it 
is.

> Documentation changes for SOLR-11003: Bi-directional CDCR support
> -----------------------------------------------------------------
>
>                 Key: SOLR-11412
>                 URL: https://issues.apache.org/jira/browse/SOLR-11412
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: CDCR, documentation
>            Reporter: Amrit Sarkar
>            Assignee: Varun Thacker
>         Attachments: CDCR_bidir.png, SOLR-11412-split.patch, 
> SOLR-11412.patch, SOLR-11412.patch, SOLR-11412.patch, SOLR-11412.patch, 
> SOLR-11412.patch
>
>
> Since SOLR-11003: Bi-directional CDCR scenario support, is reaching its 
> conclusion. The relevant changes in documentation needs to be done.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to