Details
-
Bug
-
Resolution: Unresolved
-
None
-
None
-
*Location*: https://docs.couchbase.com/server/6.0/learn/clusters-and-availability/xdcr-filtering.html
*Referrer*: https://docs.couchbase.com/server/6.0/learn/clusters-and-availability/xdcr-overview.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:73.0) Gecko/20100101 Firefox/73.0
*Screen Resolution*: 1920 x 1080*Location*: https://docs.couchbase.com/server/6.0/learn/clusters-and-availability/xdcr-filtering.html *Referrer*: https://docs.couchbase.com/server/6.0/learn/clusters-and-availability/xdcr-overview.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:73.0) Gecko/20100101 Firefox/73.0 *Screen Resolution*: 1920 x 1080
-
DOC-2020-S4-Mar08, DOC-2020-S5-Mar22, DOC-2020-S6-Apr05
-
1
Description
At the bottom of the page, we have the text:
You can provide text to replace all or part of your search string. To do this, you need to group together matches by enclosing them in parentheses,so that they can be referenced in the replacement. To reference a matched parameter, use $n where n is the parameter,starting from 1.
I'm not sure how this applies in the XDCR case, and seems to be part of a common description of regex functionality.