codope opened a new pull request, #9724:
URL: https://github.com/apache/hudi/pull/9724
### Change Logs
When schema on read is enabled and user drops a column, then the commit goes
through and column is dropped but `schemaId` is incorrecty set to
`maxColumnId`. This is a bug. Firstly, drop column is a delete action which
should not change the `maxColumnId`. Secondly, `schemaId` must always map to
the commit time producing the schema change otherwise it breaks on the reader
side or subsequent writes when schema on read is enabled.
### Impact
Bug fix.
### 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_
- _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]
