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

   ### Change Logs
   
   Whem using custom key generator with timestamp field with type 
`EPOCHMILLISECONDS` and output date format as `yyyy/MM/dd`, partition parsing 
fails because partition column is thought to be of LongType even though it is 
string. 
   Another issue is that if there are multiple partition fields with cusotm 
keygen, then lazy listing fails due to parsing of partitions with non-encoded 
slashes. This PR fixes these issues. 
   
   It also adds a test to check partition pruning kicks in for 
TimestampBasedKeyGenerator.
   
   ### Impact
   
   Fixes couple of bugs bug when using custom keygen with timestamp fields.
   
   ### Risk level (write none, low medium or high below)
   
   medium
   
   Eager listing in case of custom keygen with multiple fields can be costlier 
but functional. Before this patch, it wasn't even functional.
   
   ### 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