[HUDI-8830] use maxLatestCommitTime to compute splitLatestCommitDelay

[LXin96]

Change Logs

currently, we use now() - splitLatestCommit, however, when the time goes and the task just processes a huge data commit, then the diff between now and splitLatestCommit may get larger. so we may let reader operator holds a maxLatestCommitTime attribute to record the max split latestcommit time has got, and then use it to compute splitLatestCommitDelay

Impact

Describe any public API or user-facing feature change or any performance impact.

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

If medium or high, explain what verification was done to mitigate the risks.

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

[danny0405]

currently, we use now() - splitLatestCommit, however, when the time goes and the task just processes a huge data commit

@LXin96 Did you mean reading the history data set in one shot?

[hudi-bot]

CI report:

• 9b56ed299fbe60d890e5078bdff0250e1532cab7 Azure: FAILURE

Bot commands

@hudi-bot supports the following commands:

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

[LXin96]

@danny0405 nice to get reply. yes, when table just left one shot, and the shot has many inputsplits, then once a inputsplit close, a split delay will get and use (now - splitlatestcommit). Of course, when the table's produce job is a flink job, and it cp interval is half an hour, down stream job read slow, then use (now - latestcommit) may bigger than the (issued instant - splitlatestcommit). so hope the reader operator may hold a variable to record the max issued instant and use (maxLatestcommitTime - splitlatestcommit)

[danny0405]

so hope the reader operator may hold a variable to record the max issued instant and use (maxLatestcommitTime - splitlatestcommit)

But what is the meaning of this metric, even though the reader delay much we can still a small value for it.