krishan1390 opened a new pull request, #18581: URL: https://github.com/apache/pinot/pull/18581
## Summary When a multi-op ZK transaction fails, the rolled-up `KeeperException` does not tell the operator which op within the batch caused the failure. This adds per-op diagnostics so on a failed `multi()` we log, for each op in the batch, the path, the op type (create / set / delete / check), and the per-op result code from `KeeperException.getResults()`. - No behavior change — purely observability. - Strengthens the existing `testBadVersionAtomicRollback` test to assert that `KeeperException.getResults()` is populated on failure (the precondition the new logging relies on). ## Test plan - [x] `./mvnw -pl pinot-common -am test -Dtest=ZkMultiWriteBuilderTest` - [ ] Manual: trigger a `BadVersionException` against a live ZK and verify the new per-op log lines pinpoint the offender. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
