Details
Description
Lithium has a feature of handling revocation of channel access:
however, the feature will mainly focus on purging docs while the docs owner (user) leaves the channel of the docs belong to.
I have the following scenarios observed in 2.8 (as well as 2.8.x) need to be also covered by Lithium channel access improvement:
- create a doc on CBL with channels, replicate (continuous=true) the doc to SGW, on CBL remove all channels the doc was assigned, the doc gets auto purged on CBL (currently the doc stay with empty channel data)
- create a doc on CBL with channels, replicate (continuous=true) the doc to SGW, on SGW remove all channels the doc was assigned, the doc gets auto purged on CBL (currently docs stay with empty channel data)
- create a doc on SGW with channels, replicate (continuous=true) the doc to CBL, on SGW remove all channels the doc was assigned, the doc gets auto purged on CBL (currently it works expected)
- create a doc on SGW with channels, replicate (continuous=true) the doc to CBL, on CBL remove all channels the doc was assigned, the doc gets auto purged on CBL (currently docs stay with empty channel data)
Discussed my observations with Adam and Pasin Suriyentrakorn , will confirm if a CBL doc with empty channel should be purged or not.
Attachments
Issue Links
- relates to
-
CBL-1225 Testfest : unshare the docs does not replicate to CBL
- Closed