Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.1.0-rc0, 8.0.4, 7.0.16, 6.0.20
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

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

v8.0, v7.0, v6.0
Sprint:
Execution Team 2022-10-17, Execution Team 2022-10-31, Execution Team 2022-11-14, Execution Team 2022-11-28, Execution Team 2024-09-02, Execution Team 2024-09-16

Instead of rounding timestamps down as expected, the server will round the bucket's minimum timestamp up for pre-1970 dates. (More accurately, it rounds the timestamp, expressed as an offset from the Unix epoch, towards zero.) This can result in incorrect control.min time values.

is duplicated by

SERVER-77889 Timeseries sharded on time can route pre-1970 inserts incorrectly

Closed

is related to

SERVER-94228 Support Date_t formatting and parsing of dates before 1970

Backlog

related to

SERVER-77888 Timeseries last-point query is incorrect for pre-1970 dates

Backlog

SERVER-77889 Timeseries sharded on time can route pre-1970 inserts incorrectly

Closed

SERVER-93874 $group on time-series collections can produce rounded results due to bucket control rounding

Closed

SERVER-67825 Investigate where time-series functionality relies on control summary timestamps

Closed

(1 related to)

Assignee:: Henrik Edin

Reporter:: Dan Larkin-York

Participants:: Dan Larkin-York, David Percy, Githook User, Henrik Edin

Votes:: 0 Vote for this issue

Watchers:: 13 Start watching this issue

Created:: Jul 06 2022 05:26:53 PM UTC

Updated:: Dec 09 2024 04:01:38 PM UTC

Resolved:: Sep 04 2024 12:18:08 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates