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

[Bug][Sort] Iceberg data is messed up when the source table has no primary key in multiple sink scenes #6382

Closed
2 tasks done
thesumery opened this issue Nov 2, 2022 · 0 comments · Fixed by #6383 or #6461
Closed
2 tasks done
Assignees
Labels
component/sort type/bug Something is wrong
Milestone

Comments

@thesumery
Copy link
Contributor

What happened

Iceberg miss data when source table do not have primary key in multiple sink scences

What you expected to happen

Iceberg miss data when source table do not have primary key in multiple sink scences

How to reproduce

Submit a Iceberg multiple sink task , and prepare a table without primary key in source table.

Environment

No response

InLong version

master

InLong Component

InLong Sort

Are you willing to submit PR?

  • Yes, I am willing to submit a PR!

Code of Conduct

@thesumery thesumery added the type/bug Something is wrong label Nov 2, 2022
@healchow healchow added this to the 1.4.0 milestone Nov 3, 2022
@healchow healchow changed the title [Bug][Sort] Iceberg miss data when source table do not have primary key in multiple sink scences [Bug][Sort] Iceberg misses data when the source table has no primary key in multiple sink scenes Nov 3, 2022
@thesumery thesumery changed the title [Bug][Sort] Iceberg misses data when the source table has no primary key in multiple sink scenes [Bug][Sort] Iceberg data is messed up when the source table has no primary key in multiple sink scenes Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment