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

   ### Change Logs
   
   _Describe context and summary for this change. Highlight if any code was 
copied._
   
   Refer to JIRA HUDI-5686 for detailed description of the issue.
   Approach here is to avoid creation of new instants (timestamps) for 
rollbacks when there are rollbacks of incomplete commits in the timeline 
created by previous runs. Instead of creating new instants, I'm reusing the 
timestamp to create rollback instant which abides with the chronological order 
of the commits.
   
   ### Impact
   
   _Describe any public API or user-facing feature change or any performance 
impact._
   No breaking changes
   
   ### Risk level (write none, low medium or high below)
   
   _If medium or high, explain what verification was done to mitigate the 
risks._
   Low, verified data correctness against source database in production for 50+ 
HoodieDeltaStreamer jobs running in both batch and continuous modes. 
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change_
   
   - _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
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Change Logs and Impact were stated clearly
   - [x] Adequate tests were added if applicable
   - [x] 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