parisni opened a new pull request, #11670:
URL: https://github.com/apache/hudi/pull/11670
### Change Logs
This PR addresses ongoing issue with glue and athena/redshift-spectrum query
engines:
currently in some schema evolution scenario (see below), the modified
columns can't be read.
It does not affect spark. partially fixes #11599
This PR is based on #9071 with some changes:
- rebase on master
- make use of existing update partition method
- cascade when needed
Few facts about cascading schema on partitions:
- if a new column is added to the table -> NO NEED
- if a column is dropped -> NO NEED
- if a struct gets a new field as the last one -> NO NEED
- if a struct get a new field between existing fields -> NEEDED
- if a column is type promoted -> NEEDED
### Impact
In case the table will have schema difference matching the rules above, the
glue sync will take the time to update every partitions within glue.
### Risk level (write none, low medium or high below)
Low
### 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]
