-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
GH-3617 : Value parameters in ReactiveKafkaProducerTemplate should be nullable #3651
Conversation
jukekxm
commented
Nov 26, 2024
- Fixes : Value parameters in ReactiveKafkaProducerTemplate should be nullable #3617
- add @nullable to parameter of send method
- Fix to allow tombstone records to be transferred.
@kimjuke Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@kimjuke Thank you for signing the Contributor License Agreement! |
@@ -33,6 +33,7 @@ | |||
import reactor.kafka.sender.SenderRecord; | |||
import reactor.kafka.sender.SenderResult; | |||
import reactor.kafka.sender.TransactionManager; | |||
import reactor.util.annotation.Nullable; |
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 are we using the Nullable
annotation from the reactor project? Since we are in a Spring library, using Spring's org.springframework.lang.Nullable
is okay. Could you change it?
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.
Thanks for your review!
I modified the package as you mentioned.
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.
Could you add your name to the author list?
@sobychacko I added my name, Thank you. |
PR is failing due to checkstyle errors. Can you fix those?
|
I fixed them. Thank You :) |
@jukekxm Thanks for the PR. It is now merged upstream. |