autoCAT6 opened a new pull request, #18533:
URL: https://github.com/apache/iceberg/pull/18533

   Azure bulk deletion can report success after storage failures because it 
calls the best-effort single-file deletion method, which suppresses exceptions. 
Call the SDK's idempotent delete from the bulk task so failures reach the 
existing aggregate counter, while missing files remain successful and 
single-file deletion keeps its current behavior. This narrows the Azure gap 
previously identified in #16444 and reported downstream in apache/polaris#5482. 
End-to-end Polaris retry behavior also depends on its separate caller change in 
apache/polaris#5421 and adoption of this Iceberg fix.
   
   Tests cover 403/5xx/runtime failures, partial-batch failure counts and 
completion, missing files and repeated deletion, successful/empty batches, and 
unchanged single-file behavior. The same 13 regressions change from 8 passes/5 
failures on the baseline to 13 passes. The full Azure unit suite passes all 86 
tests; module assembly/Javadoc, Spotless and Checkstyle main/test also pass.
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to