-
Notifications
You must be signed in to change notification settings - Fork 14k
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
KAFKA-5171 : TC should not accept empty string transactional id #2973
Conversation
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
@guozhangwang please review this PR and let me know if that serves the purpose. Can we also refactor TransactionCoordinator.handleInitPid() to leverage the existing validateTransactionalId() method? |
@umesh9794 thank you for the PR. I think the purpose is to accept null |
Refer to this link for build results (access rights to CI server needed): |
Ah..sorry I missed that null should be accepted, thanks for the review @guozhangwang. I have updated the PR. Sure will wait to rebase this PR after those commits and thanks again for telling this in advance :) |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
KAFKA-5171 : TC should not accept empty string transactional id
@guozhangwang should I rebase it now or some more changes are about to be pushed? |
Refer to this link for build results (access rights to CI server needed): |
Refer to this link for build results (access rights to CI server needed): |
The major changes have been pushed, feel free to rebase now. |
@guozhangwang . I rebased the changes and created a new PR because I got messed with many conflicts in this PR. Please review that updated PR and let me know your comments. |
This is an initial PR. Changed the unit tests accordingly as per the expectation from TC.