the-other-tim-brown opened a new pull request, #6806:
URL: https://github.com/apache/hudi/pull/6806

   ### Change Logs
   
   After discussing the current implementation with other Protobuf users, there 
were a few asks around handling some types better.
   
   1. Handle unsigned longs as a decimal (backed by a fixed size byte array) in 
avro to allow users to query these fields within their lake without converting 
to an unsigned long after reading the data or when writing the query (currently 
unsigned long is just stored as a signed long)
   2. Handle timestamps by converting them to a long with the timestamp-micros 
logical type in avro
   3. Make fields within a `oneOf` nullable since only one of them will ever be 
set
   4. Change the default settings for handling wrapped primitives to just treat 
them as nullable primitives
   
   ### Impact
   
   Default settings are updated but this feature is not yet released (part of 
0.13.0 release)
   
   **Risk level: low **
   
   ### 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
   
   - [ ] 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