Repository navigation
UpdateTimeToLive and DescribeTimeToLive during a table's DELETING window answer differently from DynamoDB #552
Description
Summary
During a table's DELETING window the service serves UpdateTimeToLive and refuses DescribeTimeToLive with its own sentence; ExtendDB does the opposite.
Request during DELETING |
Service (measured 2026-10-25) | ExtendDB (PostgreSQL and MongoDB measured; main 744ea29 and #550) |
|---|---|---|
UpdateTimeToLive enable |
200 {Enabled: true, AttributeName: ttl} |
400 ResourceInUseException Table <name> is not in ACTIVE state |
DescribeTimeToLive |
400 ValidationException Cannot describe time to live while table is in DELETING state: Current table state is DELETING |
200 {TimeToLiveStatus: DISABLED} |
Cause
crates/engine/src/ttl.rs and the backends' TTL paths require ACTIVE for the update and do not check the status for the describe. #550 adds the TableBeingDeleted arm to the TTL error mapper, so a backend that returns the variant renders the DELETING sentence; none does yet.
Fix shape
Serve UpdateTimeToLive on a DELETING row (the write is to the catalog row, which goes with the table) and refuse DescribeTimeToLive with the measured sentence. Two dual-target wire rows on the held-window fixture.
Found while reviewing #505.
Metadata
Metadata
Assignees
Labels
No labels
Activity
LeeroyHannigan commentedon Oct 25, 2026
Repeated the two rows on 2026-10-25, three rounds, each call issued while
DescribeTablereadDELETING(the status is checked right before every call and the row is skipped otherwise; none was skipped). Added the follow-on calls a fix has to answer.DELETINGENABLEDonttlbefore the delete)DescribeTimeToLiveValidationExceptionCannot describe time to live while table is in DELETING state: Current table state is DELETINGUpdateTimeToLiveenablettl{TimeToLiveSpecification: {Enabled: true, AttributeName: ttl}}ValidationExceptionTimeToLive is already enabledDescribeTimeToLiveafter the enableDELETINGsentence againUpdateTimeToLivedisablettlright afterValidationExceptionTime to live has been modified multiple times within a fixed intervalUpdateTimeToLiveenableexpiresValidationExceptionTimeToLive is active on a different AttributeName: current AttributeName is ttlSo during the window
UpdateTimeToLiveruns its ordinary rules against the catalog row (the enable persists within the window: the disable is rate limited and the other attribute is refused as a conflict), and onlyDescribeTimeToLivehas aDELETINGsentence. The fix servesUpdateTimeToLiveon aDELETINGrow with the same rules as on anACTIVEone and refusesDescribeTimeToLivewith the sentence above.The window on the service was 3 to 5 s in these rounds; every row was measured inside it, and the table read
ResourceNotFoundExceptionafterwards.