Details
-
Improvement
-
Resolution: Fixed
-
Major
-
7.6.0
-
0
Description
Currently the behavior in 7.2 and earlier is,
| Bucket maxTTL value | What the value represents |
|---|---|
| 0(default) | No expiry. Documents do not expire |
| Any positive integer | Number of seconds document documents will live |
| Collection maxTTL value | What the value represents |
|---|---|
| 0(default) | Use bucket's maxTTL value |
| Any positive integer | Number of seconds document documents will live |
This doesn't allow for setting no-expiry on a collection. It was decided to accept a new value of "-1" for maxTTL which would mean that we disable expiry for that collection.
Changes need to made to,
POST pools/default/buckets/bucketName/scopes/scopeName/collections
PATCH pools/default/buckets/bucketName/scopes/scopeName/collections/collectionName
PUT pools/default/buckets/bucketName/scopes
The new value for -1 will be reflected in the GET API, pools/default/buckets/bucketName/scopes
Attachments
Issue Links
- blocks
-
CM-1132 collection API support a new value of -1 for maxTTL
-
- To Do
-
-
-
- Closed
-
- depends on
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
MB-59927
UI: maxTTL behavior changed in the server the UI should account for the same
-
- Open
-
Gerrit Reviews
| For Gerrit Dashboard: MB-59772 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 202000,4 | MB-59772 Support "no expiry" for collection (maxTTL=-1) | master | ns_server | Status: MERGED | +2 | +1 |
| 202082,3 | MB-59935 Replace use-bucket-ttl with no-expiry | master | couchbase-cli | Status: MERGED | +2 | +1 |
| 202243,4 | MB-59934 Fix for ns_server maxTTL changes | master | backup | Status: MERGED | +2 | +1 |
| 202294,1 | MB-59772 Support "no expiry" for collection (maxTTL=-1) | master | ns_server | Status: ABANDONED | 0 | +1 |
| 202383,2 | MB-59772 Re-add code lost when change-id changed. | master | ns_server | Status: MERGED | +2 | +1 |