Pandas886 opened a new issue, #8565: URL: https://github.com/apache/seatunnel/issues/8565
### Search before asking - [x] I had searched in the [issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22) and found no similar issues. ### What happened source ``` FakeSource { result_table_name = "fake" row.num = 300 int.min = 1 int.max = 300 schema = { fields { name = "string" id = "int", age="int" } } } ``` paimon schema ``` { "version" : 3, "id" : 0, "fields" : [ { "id" : 0, "name" : "name", "type" : "STRING" }, { "id" : 1, "name" : "id", "type" : "INT NOT NULL" }, { "id" : 2, "name" : "age", "type" : "INT NOT NULL" } ], "highestFieldId" : 2, "partitionKeys" : [ ], "primaryKeys" : [ "id" ], "options" : { "bucket" : "-1", "file.format":"orc", "manifest.format" : "orc", "dynamic-bucket.target-row-num":"30" }, "timeMillis" : 1731551425602 } ``` After multiple writes to the paimon dynamic bucket table from the source, the same primary key was not merged, resulting in duplicate data.  The issue appears to be related to rows with the same primary key not being assigned to the same bucket. ### SeaTunnel Version 2.3.8 ### SeaTunnel Config ```conf NAN ``` ### Running Command ```shell NAN ``` ### Error Exception ```log NAN ``` ### Zeta or Flink or Spark Version FLINK 1.18 ### Java or Scala Version _No response_ ### Screenshots _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
