[MINOR] Make HoodieTable AutoCloseable and close per-cycle tables in BaseHoodieTableServiceClient

[Davis-Zhang-Onehouse]

Change Logs

A HoodieTable created per table-service work unit on the driver lazily builds a FileSystemViewManager. For a SPILLABLE_DISK view the file-group store spills to an on-disk BitCaskDiskMap (which registers a JVM shutdown hook). HoodieTable had no close(), and the per-cycle tables created in BaseHoodieTableServiceClient were never closed, so their cached views' on-disk maps lingered until JVM exit.

• HoodieTable now implements AutoCloseable; close() releases the FileSystemViewManager and the table metadata reader (idempotent, never throws).
• Every create-use-drop HoodieTable in BaseHoodieTableServiceClient is wrapped in try-with-resources / try-finally: preCommit, logCompact, compact, cluster, scheduleTableServiceInternal, scheduleCleaning, purgePendingClustering, clean, rollbackFailedIndexingCommits, rollback, rollbackFailedBootstrap. (commitCompaction/commitLogCompaction are left alone — they receive an Option<HoodieTable> that may be caller-owned.)
• SpillableMapBasedFileSystemView now drains its ExternalSpillableMaps from closeResources() — under the AbstractTableFileSystemView writeLock — instead of from close() before the lock. This releases the on-disk maps while still referenced and without racing a concurrent reader.
• Adds TestHoodieTableResourceLifecycle verifying that HoodieTable.close() releases the spillable view's on-disk BitCaskDiskMap.

Impact

Promptly frees per-cycle driver-side file-system view resources instead of leaving them until JVM exit. No behavior change to table-service results.

Risk level: low

Lifecycle change covered by existing file-system-view close tests plus the new test.

Companion internal PR

This is kept code-consistent with the Onehouse-internal companion (onehouseinc/hudi-internal#1959). The internal repo additionally needs the closeResources() ordering fix as an actual bug fix (its SpillableMapBasedFileSystemView overrides closeResources() and was calling super first, nulling the map fields before draining them); here the same drain-before-super ordering is applied for the writeLock benefit.

Documentation Update

None.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable

[codecov-commenter]

Codecov Report

❌ Patch coverage is 50.00000% with 29 lines in your changes missing coverage. Please review.
✅ Project coverage is 51.04%. Comparing base (d5c6b4d) to head (255eaf2).
⚠️ Report is 90 commits behind head on master.

Files with missing lines	Patch %	Lines
...ache/hudi/client/BaseHoodieTableServiceClient.java	46.66%	21 Missing and 3 partials ⚠️
...c/main/java/org/apache/hudi/table/HoodieTable.java	61.53%	4 Missing and 1 partial ⚠️

❗ There is a different number of reports uploaded between BASE (d5c6b4d) and HEAD (255eaf2). Click for more details.

HEAD has 27 uploads less than BASE

Flag	BASE (d5c6b4d)	HEAD (255eaf2)
hadoop-mr-java-client	1	0
spark-scala-tests	10	0
spark-java-tests	15	0
utilities	1	0

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #19042       +/-   ##
=============================================
- Coverage     68.78%   51.04%   -17.74%     
+ Complexity    29136    20833     -8303     
=============================================
  Files          2515     2457       -58     
  Lines        139938   133008     -6930     
  Branches      17187    15628     -1559     
=============================================
- Hits          96260    67898    -28362     
- Misses        35902    59726    +23824     
+ Partials       7776     5384     -2392     

Flag	Coverage Δ
common-and-other-modules	44.78% <48.27%> (+0.44%)	⬆️
hadoop-mr-java-client	?
spark-client-hadoop-common	48.35% <18.96%> (+0.12%)	⬆️
spark-java-tests	?
spark-scala-tests	?
utilities	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...c/main/java/org/apache/hudi/table/HoodieTable.java	69.72% <61.53%> (-19.77%)	⬇️
...ache/hudi/client/BaseHoodieTableServiceClient.java	58.28% <46.66%> (-16.80%)	⬇️

... and 1164 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[hudi-bot]

CI report:

• 839de89 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

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