[HUDI-8858]Support ShowRecordLocationProcedure

[houyuting]

Change Logs

Add show record location procedure feature , The pr is aim to locate the bucket id and then the hdfs data file through the record key, it is faster compared to select ${record_key} from table.

Impact

none

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

none

Documentation Update

none

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:

• 1cfba1a Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[yuzhaojing]

Thanks for your contribution, left some comments.

[yuzhaojing]

Is this procedure only applicable to the bucket index? Can we extend it to all index types? Alternatively, we can add the verification of the bucket index in this pull request (PR) and deal with the remaining index types directly in subsequent pull requests.

[yuzhaojing]

Can it support multiple record keys?

[danny0405]

The task is not minor, can you create a JIRA task to trace it.

[TheR1sing3un]

Nice work!
But I think if we could implement a more general procedure instead of just using it for bucket indexes? Instead of passing in the record_key, we pass in the primary key/index columns and then we tag the table based on its own index to find the corresponding file group or even file name.
Thanks for your contribution, this procedure can be combined with cli tools later, which can greatly improve our daily troubleshooting efficiency.