-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Master Build Fixes - AclAuthorizer and TransformValues Replacement #10645
Open
hrishabhg
wants to merge
58
commits into
master
Choose a base branch
from
fix-master-build-jan-2025
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+360
−168
Open
Changes from all commits
Commits
Show all changes
58 commits
Select commit
Hold shift + click to select a range
87aa49e
Use assertEquals instead
VedarthConfluent b4ec319
Fix assert statement
VedarthConfluent c10bc81
Fix asser equals
VedarthConfluent dbeaef1
Fix tests
VedarthConfluent ecd9e6a
Fixes a test
VedarthConfluent 600b73d
Revert test updates
VedarthConfluent dd790e6
Encode the test url
VedarthConfluent 700a0d6
Revert url encoding
VedarthConfluent 0d4da08
fix: replaced transformer with processor for sinkbuilder
hrishabhg 788a093
refactor: renamed vars
hrishabhg 31e0b56
refactor: reverted changes
hrishabhg 2ed9f5c
refactor: renamed parameter with better name
hrishabhg 71dba6d
fix: replaced ksqltransformer with ksqlprocessor
hrishabhg fe41cff
fix: replaced ksqltransformer with ksqlprocessor
hrishabhg 525f2f3
fix: kstream transformer replaced with processor
hrishabhg adca69f
fix: fixed tests
hrishabhg 15687d3
fix: fixed tests for streambuilder
hrishabhg fdec55e
fix: fixed tests for streambuilder
hrishabhg e634d5f
fix: fixed test
hrishabhg 4c17c6f
refactor: simplified ksprocessor
hrishabhg f16b882
refactor: interface implementation simplified
hrishabhg 04a5e31
refactor: renamed transform with process
hrishabhg afdf679
refactor: renamed with kstream convention
hrishabhg fd05218
fix: added test for ksprocessor and ksfixedkeyprocessor
hrishabhg 08fb0d2
fix: updated the fakestream impl
hrishabhg 8515e5c
fix: updated stream topology collection in test
hrishabhg 72f9419
fix: fixed tests
hrishabhg 9f21f2a
fix: ignore postAggregationMapper Tes
hrishabhg b35ee9c
fix: fixed pre-agg test
hrishabhg d225a84
fix: fixed pre-agg test
hrishabhg fa8d6df
fix: checkstyle for unused import
hrishabhg 6c4c4ff
attempt to fix backward incompatibility
mjsax 4ca4f40
fix: burn index by peek
hrishabhg 8ed2f1a
fix: checkstyle-removed unused imports
hrishabhg 88f5c83
fix: test
hrishabhg 9ef8c4a
fix: test
hrishabhg 4cbeb83
fix: checkstyle fix
hrishabhg d086480
fix: fixed historical plan tests
hrishabhg fff5571
fix: reverted semaphore
hrishabhg 06523fe
fix: fixed the error message check
hrishabhg 1757a55
fix: updated historical plans version
hrishabhg 7f7c9bf
Merge branch 'master' into master-build-failure-18122024
hrishabhg a3033d6
fix: removed ksqlprocessingctx usage
hrishabhg 43344d5
fix: removed rowtime checks
hrishabhg 24655f6
refactor: refactored for consistency
hrishabhg ecbbdaa
Merge branch 'master' into transformer-migration-2
hrishabhg 6810fef
refactor: imported namespace FixedKeyProcessorContext
hrishabhg 2b3ff5f
fix: replaced aclauthorizer with standardauthorizer for tests
hrishabhg f355cdc
fix: replaced stream.transformValues with stream.processValues
hrishabhg 6186a19
fix: tests errors fixed
hrishabhg ceda846
fix: fixed tests
hrishabhg 224e94c
Merge branch 'master' into fix-master-build-jan-2025
hrishabhg 47c0d60
fix: fixed tests
hrishabhg c4c82df
fix: replaced transformvalues with processvalues for test
hrishabhg 5537aa5
fix: replaced transformvalues with processvalues for test
hrishabhg d25923a
fix: added stream.peek hack for maintaining the state
hrishabhg 1df46ba
fix: added named.class in test
hrishabhg 80dd096
fix: added named.class in test
hrishabhg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this node named explicitly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have done as per test case requirement. I have asked kstream team if this looks okay. It was generating
KSTREAM-PROCESSVALUES-0000000001
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Processor
name by themself should actually not be critical if they change. We need to worry about topic and state store names though.What break if the processor name changes? If it's really only the name, it should be ok to accept the change and update the tests. If it has side-effects, setting the name here would sound rights.
The other question is, if we name explicitly, could it cause side-effect with regard to auto-naming of downstream processor -- if we name expliclity, we might not us the next index, and create different name later, what could also lead to undesried side effects.