[revert] "[improve][ml] Do not switch thread to execute asyncAddEntry's core logic (#23940)" #23994
+31
−90
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.
This reverts commit 215b36d.
Motivation
See some discussion details in #23983.
#23940 and #23983 (not merged) both change the semantic for
ManagedLedgerInterceptor#beforeAddEntry:ManagedLedgerImplManagedLedgerImpl#asyncAddEntryin the same thread.Since managed ledger and the interceptor are both pluggable (the interceptor can be changed via configuring
BrokerEntryMetadataInterceptoror evenManagedLedgerConfig#setManagedLedgerInterceptor), the semantic change should require a formal PIP. Before that, the downstream applications should only rely on specific implementation details and hack intoManagedLedgerImpl.Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository: