perf(fs-view): skip bootstrap index init for non-bootstrap tables to cut S3 HEAD calls

[wangxianghu]

Describe the issue this Pull Request addresses

For non-bootstrap tables, skip initializing the real bootstrap index and use a NoOp implementation instead. HFileBootstrapIndex's constructor issues two storage.exists() probes (plus a reflective class load) on every view init; on object stores like S3 each probe is a billable HEAD request, so for the common case where no bootstrap able exists this is a pure waste of latency and money. useIndex() already short-circuits to false when the bootstrap base path is absent, so swapping in NoOpBootstrapIndex is behavior-preserving while cutting those S3 API calls.

Summary and Changelog

Init BootstrapIndex as NoOpBootstrapIndex when is not bootstrap table to avoid call s3 api to save money

Impact

None

Risk Level

low

Documentation Update

none

Contributor's checklist

• Read through contributor's guide
• Enough context is provided in the sections above
• Adequate tests were added if applicable

[wangxianghu]

hi @yihua, do you have time to review this ?

[hudi-agent]

⚠️ 🤖 This review was generated by an AI agent and may contain mistakes. Please verify any suggestions before applying.

Thanks for the contribution! This PR substitutes a NoOpBootstrapIndex for non-bootstrap tables to avoid the two storage.exists() probes (billable S3 HEAD requests) that HFileBootstrapIndex's constructor issues on every file-system-view init. The change is behavior-preserving: useIndex() is final in the base class and already requires a configured bootstrap base path, so when the path is absent every index implementation returns false, and all createReader() call sites are guarded by useIndex() — meaning the NoOp's throwing methods are never reached. No issues flagged from this automated pass — a Hudi committer or PMC member can take it from here for a final review.

cc @yihua

[hudi-bot]

CI report:

• 76cab93 UNKNOWN
• bc5cd71 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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

[yihua]

hi @yihua, do you have time to review this ?

Thanks for raising this PR. Let me take a look. Previously we had this temporary fix #12076 but there was concern around the impact on existing tables.