Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rename ResolvedTS to a understandable name #16708

Open
6 tasks
zhangjinpeng87 opened this issue Mar 27, 2024 · 0 comments · May be fixed by #16727, tikv/pd#8012, pingcap/tidb#52297 or pingcap/tiflow#10872
Open
6 tasks

Rename ResolvedTS to a understandable name #16708

zhangjinpeng87 opened this issue Mar 27, 2024 · 0 comments · May be fixed by #16727, tikv/pd#8012, pingcap/tidb#52297 or pingcap/tiflow#10872
Assignees
Labels
type/enhancement Type: Issue - Enhancement

Comments

@zhangjinpeng87
Copy link
Member

zhangjinpeng87 commented Mar 27, 2024

Background

The resolved_ts is used in TiKV, TiCDC, BR, TiDB, and many documentations like https://docs.pingcap.com/tidb/stable/ticdc-architecture. The term resolved_ts is hard to understand both on engineers' perspective and users' perspective.

In order to make the semantic more clearly, make the document more easy for our users, we should use a better alternative name for resolved_ts. The resolved_ts essentially is a watermark which is used by CDC, PiTR, flashback and EBS snapshot backup, etc.

Task Breakdowns

Timeline plan: merge after 8.1 LTS released.

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