[HUDI-6724] Initializing prevInstance to HoodieTimeline.INIT_INSTANT_TS to avoid partial reading of first commit

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.14.0
• Labels: pull-request-available
• Assignee: Unassigned
• Reporter: Lokesh Lingarajan
• Created: 18/Aug/23 05:20
• Updated: 17/Oct/23 01:24
• Resolved: 12/Sep/23 12:46

Description

Since object based incr jobs now have batching with in the commit, we can end-up in a situation for the first commit where prevInstance is same as startInstance according to existing code for batches within the first commit. 

In this scenario when we incremental query rows > prevInstance, we will skip the first commit as startInstance is also pointing to the same commit.

This is due to defaulting prevInstance to startInstance in 
generateQueryInfo API. 

Fix is to have this default to HoodieTimeline.INIT_INSTANT_TS so batching can continue on the first commit

Issue Links

• links to: GitHub Pull Request #9473