[HUDI-9571] Avoid scanning timeline to fetch InternalSchema for schema evolution

[cshuo]

Change Logs

Avoid scanning timeline to fetch InternalSchema for schema evolution

Impact

Improve performance for getting InternalSchema for schema evolution.

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. 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.

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:

• 731197b Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[cshuo]

cc @xiarixiaoyao plz take a look if you have time.

[danny0405]

@xiarixiaoyao I landed it first because the change is striaght-forward, can you double check this change?

[xiarixiaoyao]

@cshuo This modification is acceptable.
One small suggestion: Currently, we're placing historical schemas in .schema dir because we're concerned about the schema information becoming too large.
but In practice, our production environment doesn't involve frequent schema changes. Could we consider storing historical schema information directly in the commit files just like iceberg? This would significantly simply the logical of retrieving the schema information.

[danny0405]

Could we consider storing historical schema information directly in the commit files just like iceberg?

I think we can after we bring in new schema abstractions, part of RFC-88.