Revert "[HUDI-6438] Config parameter 'MAKE_NEW_COLUMNS_NULLABLE' to allow for marking a newly created column as nullable"

[geserdugarov]

Reverts commit 42799c0

Change Logs

Reverting of adding of unnecessary parameter hoodie.datasource.write.new.columns.nullable.

It started from issue 9042. The real problem was in inconsistency between Hudi table schema and Spark catalog schema. But during discussion of the issue JIRA task HUDI-6438 was created. As a results, the task was resolved by adding new parameter hoodie.datasource.write.new.columns.nullable, which is not right, because it allows to workaround implicit inconsistency in schemas. We need to provide consistency between existed schemas.

Furthermore, the real problem with inconsistency between Hudi table schema and Spark catalog schema was solved in another MR, which fixes similar former JIRA task HUDI-6219. This MR fix the issue properly. So, we don't need new parameter hoodie.datasource.write.new.columns.nullable.

Impact

Removes parameter, which allows to workaround implicit inconsistency in schemas.

Risk level (write none, low medium or high below)

Low

Documentation Update

Remove description of hoodie.datasource.write.new.columns.nullable from All Configurations list.
I will open corresponding MR to asf-site and link this MR.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[hudi-bot]

CI report:

• cf52d1b Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build