Details
-
Improvement
-
Resolution: Duplicate
-
Major
-
None
-
Security Level: Public
-
None
-
CBG Sprint 89, CBG Sprint 90
Description
Import is currently preserving document expiry by passing the existing expiry value through to the update mutation. In most scenarios this has no additional overhead - the expiry is included on the DCP mutation - but for on-demand import, an additional kv operation is required to retrieve the expiry.
gocb V2 has the ability to set a preserveExpiry flag on write operations. It would be preferable to take this approach when the sync function isn't explicitly updating the expiry.
Attachments
Issue Links
- is triggering
-
CBG-1861 Update bucket API to support 'preserveExpiry' GoCBv2 option
- Closed
-
CBG-1862 Support new bucket API change 'preserveExpiry' option for on-demand import
- Closed
- relates to
-
GOCBC-1218 Retrieve preserve expiry capability via GoCB
- Open