Skip to content

Conversation

@yash2710
Copy link
Contributor

@yash2710 yash2710 commented Nov 24, 2025

Description

Revert the change that makes crts nullable. As per internal discussion, CRTS will be backfilled with read-path filing in case of data missing.

This change is to ensure that the contract is not changed

Type of change

  • Bug fix (non-breaking change which fixes an issue)

closes #5508

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All good!

@yash2710 yash2710 changed the title Make crts non-nullable ChangeFeed: Fixes crts field being nullable Nov 24, 2025
@yash2710 yash2710 requested a review from kirillg as a code owner November 25, 2025 17:04
Copy link
Contributor

@ananth7592 ananth7592 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you describe in the PR description why this revert is required

ananth7592
ananth7592 previously approved these changes Dec 1, 2025
Copy link
Contributor

@ananth7592 ananth7592 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with a nit comment

@yash2710 yash2710 enabled auto-merge (squash) December 2, 2025 18:47
Added a check in the getter for ConflictResolutionTimestampInSeconds to throw an exception if the value is not set.
ananth7592
ananth7592 previously approved these changes Dec 2, 2025
@yash2710 yash2710 merged commit 5c22376 into master Dec 3, 2025
32 checks passed
@yash2710 yash2710 deleted the users/trivediyash/CRTS branch December 3, 2025 23:48
NaluTripician pushed a commit that referenced this pull request Jan 14, 2026
## Description

Revert the change that makes crts nullable. As per internal discussion,
CRTS will be backfilled with read-path filing in case of data missing.

This change is to ensure that the contract is not changed

## Type of change

- [x] Bug fix (non-breaking change which fixes an issue)

closes #5508
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Change Feed] ConflictResolutionTimestamp became nullable since 3.55.0

4 participants