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

   ### Describe the issue this Pull Request addresses
   
   `CompactionAdminClient.unscheduleCompactionFileId` used an AND filter that 
dropped every pending operation in the same partition except the target file 
group logic was inverted — sibling file groups were removed from the rewritten 
compaction plan.
   
   Closes #19881
   
   ### Summary and Changelog
   
   - Fix the stream filter to remove only the operation matching both the 
target `fileId` and `partitionPath` (`!(sameFile && samePart)` instead of 
`(!sameFile) && (!samePart)`).
   - Add `testUnscheduleCompactionFileIdKeepsSiblingOpsInSamePartition` in 
`TestCompactionAdminClient` with three operations in one partition; after 
unscheduling one file group, the plan must still contain the other two.
   
   ### Impact
   
   Behavior change for `unscheduleCompactionFileId` / `compaction 
unscheduleFileId`: sibling operations in the same partition remain in the 
pending plan. No API or config changes.
   
   ### Risk Level
   
   low — one-line boolean fix in admin tooling; regression test covers the 
reported scenario.
   
   ### Documentation Update
   
   none
   
   ### 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
   
   ### Test plan
   
   - [ ] `mvn test -pl hudi-client/hudi-spark-client 
-Dtest=TestCompactionAdminClient#testUnscheduleCompactionFileIdKeepsSiblingOpsInSamePartition`
   - [ ] `mvn test -pl hudi-client/hudi-spark-client 
-Dtest=TestCompactionAdminClient`
   
   
   Made with [Cursor](https://cursor.com)


-- 
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