KAFKA-19983: Fix MockProcessorContext doesn't work with WindowStores#21675
Closed
chickenchickenlove wants to merge 1 commit intoapache:trunkfrom
Closed
KAFKA-19983: Fix MockProcessorContext doesn't work with WindowStores#21675chickenchickenlove wants to merge 1 commit intoapache:trunkfrom
chickenchickenlove wants to merge 1 commit intoapache:trunkfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
After Kafka 4.0.0,
MockProcessorContextdoesn't work with WindowStores.This is a regression caused by #16906.
Some
StateStores accept aStateStoreContext, but internally require anInternalProcessorContext.Because of this, tests using
MockProcessorContextno longer work with non-logging, non-cachingWindowStores.This PR is draft based on my current understanding of the problem and one possible direction for fixing it.
I would like to use this PR as a starting point for discussion and align on the right approach with the community.