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

   ### Change Logs
   
   There is some backwards compatibility issues with reading archived timeline 
instants pre 0.8.
   
   1st issue is that Avro was upgraded in 0.12 to a version which does not 
allow for default Union to be null. This breaks reading these old instants in 
HoodieDataBlock.
   2nd issue is that it is possible for archived instants to have same 
timestamp for different actions, especially given that older versions used 
seconds for instant rather than milliseconds. However the archived timeline 
does not assume this and assumes each instant has unique timestamp.
   
   ### Impact
   
   Now the archived timeline stores a map of string (instant) -> string 
(actiontype) -> map <instant, byte[]>
   
   We also retry failures to getSchemaFromHeader with 
`.setValidateDefaults(false)` in case of AvroTypeException
   
   ### Risk level (write none, low medium or high below)
   
   _If medium or high, explain what verification was done to mitigate the 
risks._
   
   ### 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