Major Description
ns_server is implementing maxTTL=-1 (no expiry) for collections via MB-59772. This affect restore (see MB-58209). Based on the commit message for that ticket..
For backup/restore I believe this change needs to be undone as maxTTL=-1 now will mean "no expiry" (aka maxTTL disabled). The "maxTTL=0" should be retained as it means "use the bucket's maxTTL value".
1. When restoring a backup from a <7.6 cluster to a >=7.6 cluster, "maxTTL=-1" should be sent instead of "maxTTL=0", due to the change of behaviour mentioned above.
|
For this change, "maxTTL=-1" should not be sent and the nil maxTTL should be retained. Or the nil maxTTL can be changed to maxTTL=0 as both have the same meaning (use the bucket's maxTTL).
2. When restoring a backup from a >=7.6 cluster to a >=7.6 cluster, where the collection maxTTL in the backup manifest is nil, we should send "maxTTL=-1" instead, since sending a nil maxTTL would not necessarily restore the original state (see MB-58209).
|