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

   ### Change Logs
   
   If hive style partitioning is enabled, then url encoding is also enabled. We 
need to do so otherwise the partition structure is awkward in some cases. For 
example, a `partition` field with values like "dd/mm/yy" will be written as 
three-level directory where the first level is `partition=dd` and then its 
child is `mm`, and then `yy`. 
   ```
   partition=dd
                        |- mm
                              |- yy
   ```
   
   With URL encoding enabled, it will be `partition=dd%2Fmm%2Fyy`.
   
   ### Impact
   
   Correct partition strucutre. However, for a small subset of users who had 
partitions in above format and hiev style paritioning enabled, this is going to 
be a physical layout change.
   
   ### Risk level (write none, low medium or high below)
   
   medium
   
   ### 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: commits-unsubscr...@hudi.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to