[HUDI-8972] Fixing heart beats for failed writes in HoodieStreamer

[nsivabalan]

Change Logs

Every commit is expected to release resources irrespective of whether it succeeds or fail. But in HoodieStreamer, in some unhappy paths, we missed to do that. And so, the heart beat could potentially be getting updated for a failed ingestion commit which in turn will never get a chance to rollback by async workers (STS). We are fixing the resource closure ( and hence the heart beat emitting) for failed writes in HoodieStreamer in this patch.

Tests have been written to validate both happy and unhappy paths.

Impact

Robust closure of resources and heart beat stoppage for failed commits in HoodieStreamer.

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

low

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

• The config description must be updated if new configs are added or the default value of the configs are changed
• Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
  ticket number here and follow the instruction to make
  changes to the website.

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:

• 44d0a9d Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

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