[Bugfix][seatunnel-connectors-v2][connector-jdbc] Fix the bug of pgsql being written as a special field of sink #10076
+38
−26
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
Contributor
Author
Contributor
|
Are there corresponding test cases? |
Contributor
Author
#9618 |
Contributor
Author
When there are special fields on the sink side, the table structure on the sink side should be used to judge. For example, if the source is mysql and the varchar type is used to store inet content, and the target is pgsql, an error will be reported if the inet type field is used to receive data. The reason why the previous e2e could run was because the source of the test case was pgsql-cdc, and the field types were exactly the same. This was a coincidence, but it was indeed a bug. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When there are special fields on the sink side, the table structure on the sink side should be used to judge. For example, if the source is mysql and the varchar type is used to store inet content, and the target is pgsql, an error will be reported if the inet type field is used to receive data. The reason why the previous e2e could run was because the source of the test case was pgsql-cdc, and the field types were exactly the same. This was a coincidence, but it was indeed a bug.