KAFKA-14586: Moving StreamResetter to tools#13127
Conversation
|
@mjsax , I noticed you had worked on the StreamsResetter tool. Would you be able to review this smallish PR? The idea is to move it from core module to tools module which is part of this: https://issues.apache.org/jira/browse/KAFKA-14525 |
|
Adding @fvaleri . There are checkstyle issues, which I would fix. |
cadonna
left a comment
There was a problem hiding this comment.
@vamossagar12 Thanks for the PR!
I had one major comment.
f850603 to
fff2eaa
Compare
Thanks @cadonna . I think that comment has been addressed now based on the conversation. |
|
@cadonna , bumping this thread again. |
|
@vamossagar12 as you can see from the CI output, there are checkstyle errors. Have you tried to run at least one of the system tests that are using the tool? |
hi @fvaleri , yes I am aware of the checkstyle issue and pointed it out here: #13127 (comment). I have run the StreamResetter tests and also modified the system test. |
|
@vamossagar12 The PR LGTM except for the checkstyle issues. Could you also please post a link to a successful system test run of the system tests that use the streams resetter? |
|
Thanks @cadonna , would do the same. |
f9497e9 to
dda1072
Compare
|
@cadonna , @fvaleri I ran the system test for StreamsResetter from my local (and fixed the checkstyle). The tests are running, would keep an eye on it => |
|
Tests seemed to have passed for one of the builds. The tests that failed (even the one is Streams) seem unrelated to me. |
There was a problem hiding this comment.
Hi @vamossagar12, thanks for fixing the checkstyle errors.
I left a few comments. I also think that it would be better to use the shared CommandDefaultOptions class, like in all the other joptsimple tools (help and version code is duplicated here).
The system test looks good:
test_id: kafkatest.tests.streams.streams_optimized_test.StreamsOptimizedTest.test_upgrade_optimized_topology.metadata_quorum=REMOTE_KRAFT
status: PASS
run time: 1 minute 12.791 secondsThere was a problem hiding this comment.
This subpackage is not needed if you move StreamsResetterTest to tools test.
There was a problem hiding this comment.
I guess this is related to my comment #13127 (comment)?
There was a problem hiding this comment.
I think this test belongs to the tools module, where the class under test lives.
There was a problem hiding this comment.
Yeah even I had thought so. But the original layout was also similar (i.e StreamsResetter was under tools and the test lived here) so I didn't change it. @cadonna , WDYT?
There was a problem hiding this comment.
I would also move it to the tools module.
@mjsax @guozhangwang Was there a specific reason not to have the test in the same module as the StreamsResetter?
There was a problem hiding this comment.
Got it @cadonna . Would wait for the response. Even I think it can move but let's see what guozhang and Mathias have to say.
Also, while we are at it, would like to know your opinion on #13127 (comment)
There was a problem hiding this comment.
I would not wait for the answer. We can do that in a follow-up PR. Could you open a ticket for the move?
There was a problem hiding this comment.
Thanks @cadonna , here's the follow up ticket: https://issues.apache.org/jira/browse/KAFKA-14851
dda1072 to
680e971
Compare
|
Thanks for the review @fvaleri . I addressed/responded to the comments. Regarding moving to |
Hi @vamossagar12, I'm ok with doing it in a follow up PR. Do we have a Jira for that? |
Thanks @fvaleri , here you go: https://issues.apache.org/jira/browse/KAFKA-14734 |
|
Thanks @fvaleri ! |
|
@cadonna , bumping this one again :) |
|
I restarted the build. Once the results are acceptable, I will merge the PR. |
|
Test failures are unrelated: |
This PR adds CommandDefaultOptions usage like in the other joptsimple based tools. It also moves the associated unit test class from streams to tools module as discussed in apache#13127 (comment). Signed-off-by: Federico Valeri <fedevaleri@gmail.com>
This PR adds CommandDefaultOptions usage like in the other joptsimple based tools. It also moves the associated unit test class from streams to tools module as discussed in #13127 (comment) Reviewers: Luke Chen <showuon@gmail.com>, Bruno Cadonna <cadonna@apache.org>, Sagar Rao <sagarmeansocean@gmail.com>
This PR adds CommandDefaultOptions usage like in the other joptsimple based tools. It also moves the associated unit test class from streams to tools module as discussed in apache#13127 (comment) Reviewers: Luke Chen <showuon@gmail.com>, Bruno Cadonna <cadonna@apache.org>, Sagar Rao <sagarmeansocean@gmail.com>
This PR adds CommandDefaultOptions usage like in the other joptsimple based tools. It also moves the associated unit test class from streams to tools module as discussed in apache#13127 (comment) Reviewers: Luke Chen <showuon@gmail.com>, Bruno Cadonna <cadonna@apache.org>, Sagar Rao <sagarmeansocean@gmail.com>
This PR adds CommandDefaultOptions usage like in the other joptsimple based tools. It also moves the associated unit test class from streams to tools module as discussed in apache#13127 (comment) Reviewers: Luke Chen <showuon@gmail.com>, Bruno Cadonna <cadonna@apache.org>, Sagar Rao <sagarmeansocean@gmail.com>
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)