MINOR: Use TransactionOperation enum instead of String for pending state checks #21218
+23
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
this PR refactors
TransactionManager#throwIfPendingStateto use a typedTransactionOperationenum instead of a raw String.###Background / Motivation
The previous String-based API relies on manually passing operation names, which can make it easier for naming to drift or become inconsistent over time. Using an enum makes the intent more explicit and keeps the operation naming centralized.
What’s changed
TransactionOperationenum with adisplayName(andtoString()override) to preserve readable exception messages.beginTransaction,prepareTransaction,sendOffsetsToTransaction,maybeAddPartition) to pass the corresponding enum value.throwIfPendingStateto acceptTransactionOperationinstead ofString.Behavior / Compatibility
TransactionOperation#toString().Testing
No additional tests were added since this is a small refactor; existing tests should continue to cover the pending-transition behavior.