[HUDI-8552] Adding support to read input for clustering based on new FG reader

[nsivabalan]

Change Logs

• Adding support to read input for clustering based on new FG reader
• Fixed FileGroup reader to maintain a schema cache and avoid storing entire schema for every record in the spillable map.

Impact

Standardized file slice reading across all different code paths (table services)

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

medium

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

[danny0405]

Can we abstract some utility method for such config fixes?

[hudi-bot]

CI report:

• deda2f4 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[codope]

Landing this. The github action failed due to

Caused by: java.lang.NoSuchMethodError: org.apache.spark.sql.internal.SQLConf$.LEGACY_PARQUET_NANOS_AS_LONG()Lorg/apache/spark/internal/config/ConfigEntry;
  at org.apache.spark.sql.execution.datasources.parquet.SparkParquetReaderBase.read(SparkParquetReaderBase.scala:73)
  at org.apache.spark.sql.execution.datasources.parquet.HoodieFileGroupReaderBasedParquetFileFormat.readBaseFile(HoodieFileGroupReaderBasedParquetFileFormat.scala:286)
  at org.apache.spark.sql.execution.datasources.parquet.HoodieFileGroupReaderBasedParquetFileFormat.$anonfun$buildReaderWithPartitionValues$3(HoodieFileGroupReaderBasedParquetFileFormat.scala:204)

This only happens for Soark 3.3.1, while 3.3.2+ is passing. We will update the README with the supported version.