Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 6.2.0-rc0, 6.0.6
Affects Version/s: None
Component/s: None
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v6.0
Sprint:
Execution Team 2022-10-03
Linked BF Score:
8
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

The epoch test case in ttl_index_options.js uses a floating point value for the expireAfterSeconds, which should really be an integer. Even though current server semantics accept floating point values, we should update the test to use an integral type. To maintain existing test coverage, we could add a test case in to the unit test for index_key_validate::validateExpireAfterSeconds()

We could also revisit our current validation on numeric types in this ticket or in ~~SERVER-69091~~.

is related to

SERVER-10075 Should forbid illegal form of TTL indexes

Closed

SERVER-68477 Improve NaN-handling for expireAfterSeconds TTL index parameter

Closed

SERVER-69091 Handle additional out-of-bounds expireAfterSeconds values for TTL indexes

Closed

SERVER-69750 For certain index options, $listCatalog output could have inconsistent data type as $listIndexes

Closed

Assignee:: Benety Goh
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: Sep 16 2022 03:06:12 PM UTC
Updated:: Oct 29 2023 09:33:08 PM UTC
Resolved:: Sep 19 2022 03:33:26 PM UTC
Confidence Status Last Update:: 16/Sep/22 7:13 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates