Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: WT11.3.0, 8.1.0-rc0, 8.0.0-rc2
Affects Version/s: None
Component/s: APIs
Labels:
- 8.0-targeted
- SERW
- SWNA
- code-quality

Assigned Teams:

Storage Engines

Story Points:
3
Sprint:
2024-03-19 - PacificOcean, 2024-04-02 - GreatMugshot, 나비 (nabi) - 2024-04-16
Backport Requested:

v8.0

Currently, the API set_timestamp ignores when a timestamp is set to an older value than its current one; it returns success. This can be misleading and an application may think the timestamp is being moved backwards.

See ~~SERVER-84706~~ where the team has identified a call that is a silent no-op.

We should revisit this behaviour and potentially throw an error instead. We have an existing test that covers this specific scenario.

depends on

WT-12792 test/format sets timestamps while disabled in the config

Closed

SERVER-86659 Review WT_CONNECTION.set_timestamp calls

Closed

has to be done before

WT-12412 The model function set_stable_timestamp should match WT behaviour

Closed

is duplicated by

WT-11211 Setting a new stable timestamp in the past doesn't throw an error

Closed

WT-12774 failed: compatibility-test-for-newer-releases on compatibility-tests [wiredtiger @ 94e8e5ba]

Closed

related to

WT-12968 test/format (format-predictable-test) tries to set the stable timestamp in the past

Open

SERVER-84706 Investigate if setting the oldest timestamp greater than the stable timestamp can be avoided

Closed

(2 related to)

Assignee:: Etienne Petrel

Reporter:: Etienne Petrel

Votes:: 0 Vote for this issue

Watchers:: 12 Start watching this issue

Created:: Jan 29 2024 09:03:06 AM UTC

Updated:: May 09 2024 05:00:04 AM UTC

Resolved:: Apr 08 2024 11:44:40 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates