Skip Automatic Context Propagation in special operators #3845
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 change should improve performance of Automatic Context Propagation in certain cases when
doOnDiscard
,onErrorContinue
, andonErrorStop
are used.The context-propagation integration requires
contextWrite
andtap
operators to be barriers for restoringThreadLocal
values. Some internal usage ofcontextWrite
does not require us to treat the operators the same way and we can skip the ceremony of restoringThreadLocal
state as we know that noThreadLocalAccessor
can be registered for them. Therefore, a private variant is introduced to avoid unnecessary overhead when not required.Related #3840