[HUDI-5977] Fix Date to String column schema evolution

[voonhous]

Change Logs

Fix date to string schema evolution when vectorized readers are not used.

Issue and stacktrace can be found here:
https://issues.apache.org/jira/browse/HUDI-5977

Impact

Tables can be read after a date -> string schema evolution is performed and when vectorized readers are not used.

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 to make
  changes to the website.

Contributor's checklist

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

[voonhous]

@xiarixiaoyao Hello, can you please help to review the fixes here?

A test case is included to reproduce this issue + verify the fix.

Thank you.

[boundarymate]

Hello，does this PR solve the problem mentioned in https://www2.jianshu.com/p/385483e3d58f?

[voonhous]

Hello，does this PR solve the problem mentioned in https://www2.jianshu.com/p/385483e3d58f?

Erm, the issue that you've linked in the article seems to be an unrelated to the issue that is described in this PR.

[xiarixiaoyao]

@voonhous
Thank you for your contribution， LGTM

[hudi-bot]

CI report:

• 90db344 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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