HoodieBackedTableMetadata.java any API does not handle Scalable lookup needs to be revised

Example

 
* verride public HoodieData> getRecordsByKeyPrefixes(HoodieData keyPrefixes, String partitionName, boolean shouldLoadInMemory, Option> keyEncodingFn) { ValidationUtils.checkState(keyPrefixes instanceof HoodieListData, "getRecordsByKeyPrefixes only support HoodieListData at the moment"); // Apply key encoding if present

the check is added because

 
* day 1 the API took java collection as input
* later at interface level, we change it to HoodieData interface, but the underlying DAG is not necessarily able to handle big amount of RDD data.

the underlying DAG needs to be revise to be scalable before we open these APIs to take RDD based hoodie data.

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-9613
- Type: Bug
- Fix version(s):
- 1.2.0

Start in HoodieBackedTableMetadata.java at getRecordsByKeyPrefixes and inspect the HoodieData interface and underlying DAG handling described in the issue. Determine how scalable lookup should work for large or RDD-based HoodieData inputs; done means the API no longer relies on the current HoodieListData-only limitation and remains scalable.

Written by the indexing model from the issue text.