codope opened a new pull request, #13022:
URL: https://github.com/apache/hudi/pull/13022

   ### Change Logs
   
   ```
   Caused by: java.lang.IllegalArgumentException: Following instants have 
timestamps >= compactionInstant (20250322001638926001) Instants 
:[[20250322001708777__commit__COMPLETED__20250322001719795]] 
   ```
   This is thrown just after downgrading the table back to version 6 and on new 
ingestion, MDT compaction code snippet is triggered and throws this exception 
while trying to schedule compaction in mdt.
   
   This is aminly due to compaction suffix in table version 6 (or lower) that 
messes the ordering after downgrade from lsm timeline to table version 6 
timeline. Fix is to add an empty deltacommit in metadata table so that there is 
an instant greater to pass the  "timestamps >= compactionInstant" check.
   
   ### Impact
   
   MDT comapction after downgrade should succeed.
   
   ### Risk level (write none, low medium or high below)
   
   low
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change. If not, put "none"._
   
   - _The config description must be updated if new configs are added or the 
default value of the configs are changed_
   - _Any new feature or user-facing change requires updating the Hudi website. 
Please create a Jira ticket, attach the
     ticket number here and follow the 
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


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