[I] Revisit table object usage in readRecordKeysFromFileSliceSnapshot for record-level index [hudi]

["hudi-bot (via GitHub)" <gi...@apache.org>]

hudi-bot opened a new issue, #17418:
URL: https://github.com/apache/hudi/issues/17418

   The table object instantiation can be heavy and it is used by record index only in the following method.  We should revisit to see if this can be improved.
   {code:java}
   private static HoodieData<HoodieRecord> readRecordKeysFromFileSliceSnapshot(HoodieEngineContext engineContext,
                                                                               List<Pair<String, FileSlice>> partitionFileSlicePairs,
                                                                               int recordIndexMaxParallelism,
                                                                               String activeModule,
                                                                               HoodieTableMetaClient metaClient,
                                                                               HoodieWriteConfig dataWriteConfig,
                                                                               HoodieTable hoodieTable) {code}
   
   ## JIRA info
   
   - Link: https://issues.apache.org/jira/browse/HUDI-9357
   - Type: Sub-task
   - Parent: https://issues.apache.org/jira/browse/HUDI-9176
   - Fix version(s):
     - 1.1.0


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org