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

   ### Change Logs
   
   Since Flink 1.17, Flink SQL support more advanced alter table syntax.
   
   ```
   -- add a new column 
   ALTER TABLE MyTable ADD category_id STRING COMMENT 'identifier of the 
category';
   -- modify a column type, comment and position
   ALTER TABLE MyTable MODIFY measurement double COMMENT 'unit is bytes per 
second' AFTER `id`;
   -- drop columns
   ALTER TABLE MyTable DROP (col1, col2, col3);
   -- rename column
   ALTER TABLE MyTable RENAME request_body TO payload;
   ```
   Find more detail information in [Flink Alter Table SQL 
](https://nightlies.apache.org/flink/flink-docs-release-1.18/docs/dev/table/sql/alter/).
   
   We could support schema evolution by Flink SQL.
   The [last pr](https://github.com/apache/hudi/pull/10426) supports it based 
on `HoodieHiveCatalog`.
   This pr aims to support schema evolution based on `HoodieCatalog`.
   
   ### Impact
   
   None
   
   ### Risk level (write none, low medium or high below)
   
   None
   
   ### 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