-
Notifications
You must be signed in to change notification settings - Fork 140
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
chore: Remove the deprecation of statefulMapConcat operator. #1147
Conversation
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.
lgtm
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.
149302e
to
9b00834
Compare
@pjfanning PTAL, I will backport this once get merged. |
LGTM |
docs/src/main/paradox/stream/operators/Source-or-Flow/statefulMapConcat.md
Show resolved
Hide resolved
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.
lgtm - I think the warning change is ok
Motivation:
As reported in refs:#1141 , the current
statefulMap
will introduce some overhead from the allocation of tuple(State, Out)
. So let's just keep it before we come up with an allocation free version like JDK 22's gather api.Result:
Remove the deprecation of
statefulMapConcat
.Will need backport to 1.0.x branch.
Ping @JD557