In the previous "Create table with record keys and ordering fields" section, the example created a table with a partitioned column dt that was not defined in the schema. This omission will cause errors when running the SQL code, as Flink SQL requires all partitioned columns to be present in the table schema.
This commit updates sql_ddl.md to include the dt column in the table schema when using PARTITIONED BY (dt), ensuring that the example can be executed without errors. Additionally, it clarifies that all partition columns must exist in the schema to prevent similar issues.
Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
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 to make
changes to the website.
In the previous "Create table with record keys and ordering fields" section, the example created a table with a partitioned column
dtthat was not defined in the schema. This omission will cause errors when running the SQL code, as Flink SQL requires all partitioned columns to be present in the table schema.This commit updates
sql_ddl.mdto include thedtcolumn in the table schema when usingPARTITIONED BY (dt), ensuring that the example can be executed without errors. Additionally, it clarifies that all partition columns must exist in the schema to prevent similar issues.Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".
Contributor's checklist