[FLINK-39934][postgres] Fix invalid tables format error message#4442
Open
taoran92 wants to merge 1 commit into
Open
[FLINK-39934][postgres] Fix invalid tables format error message#4442taoran92 wants to merge 1 commit into
taoran92 wants to merge 1 commit into
Conversation
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 the change
This PR fixes the misleading validation error message in the Postgres pipeline connector when the configured tables value does not match the required db.schema.table format.
Previously, the error message always printed the option key tables instead of the actual invalid table value, making the configuration issue harder to diagnose.
Jira: FLINK-39934
Brief change log
No configuration option is added because this only improves the validation error message and does not change connector behavior.
Verifying this change
This change is verified by code inspection and git diff --check.
Does this pull request potentially affect one of the following parts:
Documentation
Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable