suryaprasanna opened a new pull request, #18198:
URL: https://github.com/apache/hudi/pull/18198

   ### Describe the issue this Pull Request addresses
   
   When clustering operations begin a transaction, the last completed 
transaction metadata was not being passed to the transaction manager. This 
caused the action type to not be properly identified, resulting in replaced 
file IDs being skipped during conflict resolution in `ConcurrentOperation`.
   
   ### Summary and Changelog
   
   - Pass `lastCompletedTxnAndMetadata` to `beginStateChange()` in clustering 
completion flow
   - Add `lastCompletedTxnAndMetadata` field to `BaseHoodieTableServiceClient` 
with setter
   - Populate `lastCompletedTxnAndMetadata` in table service client from write 
client during transaction initialization
   
   This ensures that during concurrent clustering operations, the conflict 
resolution mechanism properly considers replaced file IDs when detecting write 
conflicts.
   
   ### Impact
   
   This fix improves correctness of concurrent write conflict detection for 
clustering operations. Without this fix, concurrent clustering operations may 
not properly detect conflicts when files are being replaced.
   
   ### Risk Level
   
   **Low** - This change only affects the clustering conflict resolution path 
by providing additional context (last completed transaction metadata) that was 
previously missing. The change is additive and does not modify existing logic 
paths.
   
   ### Documentation Update
   
   None - This is an internal fix to the conflict resolution mechanism with no 
user-facing changes or new configurations.
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to