[SPARK-52630][SS] Reorganize streaming operator and state mgmt code and dirs #51327
+0
−0
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
anishshri-db
changed the title
anishshri-db
changed the title
|
cc - @ericm-db @HeartSaVioR - PTAL - thanks ! |
ericm-db
approved these changes
Jul 2, 2025
HeartSaVioR
requested changes
Jul 2, 2025
There was a problem hiding this comment.
Shall we lowercase the packages?
https://docs.oracle.com/javase/tutorial/java/package/namingpkgs.html
anishshri-db
force-pushed
the
task/SPARK-52630
branch
from
4f7f96c to
d5e3eb7
Compare
HeartSaVioR
approved these changes
Jul 2, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
Reorganize streaming operator and state mgmt code and dirs
Why are the changes needed?
Making it easier for operator and component extension in the future
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existing unit tests
Was this patch authored or co-authored using generative AI tooling?
No