junmuz opened a new issue, #11019:
URL: https://github.com/apache/paimon/issues/11019

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/paimon/issues) 
and found nothing similar.
   
   
   ### Paimon version
   
   2.1
   
   ### Compute Engine
   
   Spark / Paimon
   
   ### Minimal reproduce step
   
   ```
   >>> spark.sql("create table if not exists paimon.test_db.seq_tab (id INT, 
data STRING, event_ts INT, op_type STRING) TBLPROPERTIES ('primary-key'='id', 
'rowkind.field'='op_type', 'changelog-producer' = 'lookup', 'sequence.field' = 
'event_ts',  'changelog-producer.ignore-update-before' = 'true', 
'changelog-producer.row-deduplicate' = 'true')");
   DataFrame[]
   
   
   >>> spark.sql("INSERT INTO paimon.test_db.seq_tab (id, data, event_ts, 
op_type) VALUES (1, 'one', 1, '+I')")
   DataFrame[]
   
   
   >>> spark.sql("INSERT INTO paimon.test_db.seq_tab (id, data, event_ts, 
op_type) VALUES (1, 'one+', 4, '-D')")
   DataFrame[]
   
   
   # After delete a late arriving insert isn't sequenced properly
   >>> spark.sql("INSERT INTO paimon.test_db.seq_tab (id, data, event_ts, 
op_type) VALUES (1, 'one+++', 2, '+I')")
   DataFrame[]
   
   >>> spark.sql("select * from paimon.test_db.seq_tab LIMIT 
10").show(truncate=False)
   +---+------+--------+-------+
   |id |data  |event_ts|op_type|
   +---+------+--------+-------+
   |1  |one+++|2       |+I     |
   ```
   
   ### What doesn't meet your expectations?
   
   A late arriving insert shouldn't be inserted in such cases
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
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]

Reply via email to