[docs] Improve Incremental Snapshot Reading formatting and references#4472
Merged
yuxiqian merged 2 commits intoJul 14, 2026
Merged
Conversation
Contributor
Author
|
@loserwang1024, could you please review this for me? |
Member
|
Thank you for your nice patch! Could you please update the |
Contributor
Author
|
@yuxiqian thank you for your review, I updated |
yuxiqian
reviewed
Jul 14, 2026
yuxiqian
left a comment
Member
There was a problem hiding this comment.
LGTM, thank you for the contribution.
yuxiqian
approved these changes
Jul 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request?
While reading the Flink PostgreSQL CDC documentation, I found that the reference link for
scan.incremental.snapshot.enabledin the Connector Options section is incorrect. It points to an outdated anchor.Brief change log
(<br/>)for improved readability.Was generative AI tooling used to co-author this PR?