Details
-
Bug
-
Resolution: Unresolved
-
Test Blocker
-
tech-debt
-
*Location*: https://docs.couchbase.com/go-sdk/current/howtos/kv-operations.html#expiration-ttl
*Referrer*: https://docs.couchbase.com/go-sdk/current/hello-world/start-using-sdk.html
*User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36
*Screen Resolution*: 2560 x 1440*Location*: https://docs.couchbase.com/go-sdk/current/howtos/kv-operations.html#expiration-ttl *Referrer*: https://docs.couchbase.com/go-sdk/current/hello-world/start-using-sdk.html *User-Agent*: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.99 Safari/537.36 *Screen Resolution*: 2560 x 1440
-
DOC-2022-S5, DOC-2022-S8, DOC-2022-S9, DOC-2022-S13, DOC-2022-S14, DOC-2022-S15, DOC-2022-S18
Description
The "Expiration / TTL" section of the "Key Value Operations" page of the Go SDK 2.x Docs says:
If the absolute value of the expiry is less than 30 days (such as 60 * 60 * 24 * 30), it is considered an offset. If the value is greater, it is considered an absolute time stamp. For more on expiration see the expiration section of our documents discussion doc.
This is not applicable to the Go SDK: all operations including expiries (including Touch and GetAndTouch) are passed to durationToExpiry, which appropriately converts to either a Unix timestamp or absolute number of seconds depending on the expiry value. cf. https://github.com/couchbase/gocb/blob/v2.3.5/collection_crud.go#L1296
Reporter: Marks Polakovs
E-mail: marks.polakovs@couchbase.com