-
Notifications
You must be signed in to change notification settings - Fork 2k
[Bug] [Connector-V2] sink trying to update primary key in distribute sink database #9293
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
Closed
3 tasks done
Labels
Comments
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 9, 2025
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 9, 2025
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 9, 2025
4 tasks
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 9, 2025
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 9, 2025
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 13, 2025
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 13, 2025
papadave66
added a commit
to papadave66/seatunnel
that referenced
this issue
May 13, 2025
hailin0
pushed a commit
that referenced
this issue
May 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
What happened
I am trying to running seatunnel with standalone mysql database and cluster postgresql sink database.
And it gives following ERROR:
It seems that it is trying to update id's value with id condition. how to prevent updating primary columns?
SeaTunnel Version
2.3.10
SeaTunnel Config
Running Command
`seatunnel.sh --config mysql-cdc-test.conf `
Error Exception
Zeta or Flink or Spark Version
zeta with seatunnel v2.3.10
Java or Scala Version
java version "1.8.0_391"
Java(TM) SE Runtime Environment (build 1.8.0_391-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.391-b13, mixed mode)
Screenshots
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: