[GitHub] [kafka] showuon commented on pull request #13172: KAFKA-14590: Move DelegationTokenCommand to tools

2023-03-01 Thread via GitHub


showuon commented on PR #13172:
URL: https://github.com/apache/kafka/pull/13172#issuecomment-1451363118

   Failed tests are unrelated
   ```
   Build / JDK 17 and Scala 2.13 / 
org.apache.kafka.controller.QuorumControllerTest.testUnregisterBroker()
   Build / JDK 8 and Scala 2.12 / 
org.apache.kafka.connect.integration.ConnectWorkerIntegrationTest.testBrokerCoordinator
   Build / JDK 8 and Scala 2.12 / 
kafka.server.KafkaServerKRaftRegistrationTest.[1] Type=ZK, 
Name=testRegisterZkBrokerInKraft, MetadataVersion=3.4-IV0, Security=PLAINTEXT
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.clients.consumer.internals.EagerConsumerCoordinatorTest.testPrepareJoinAndRejoinAfterFailedRebalance()
   Build / JDK 11 and Scala 2.13 / 
kafka.server.DynamicBrokerReconfigurationTest.testTrustStoreAlter(String).quorum=kraft
   Build / JDK 11 and Scala 2.13 / 
kafka.server.DynamicBrokerReconfigurationTest.testTrustStoreAlter(String).quorum=kraft
   Build / JDK 11 and Scala 2.13 / 
org.apache.kafka.streams.processor.internals.StreamsAssignmentScaleTest.testHighAvailabilityTaskAssignorManyStandbys
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [kafka] showuon commented on pull request #13172: KAFKA-14590: Move DelegationTokenCommand to tools

2023-02-23 Thread via GitHub


showuon commented on PR #13172:
URL: https://github.com/apache/kafka/pull/13172#issuecomment-1441641543

   @tinaselenge ,  for (2), it looks complicated since under the tools module, 
there's no `BaseRequestTest` or `SaslSetup` to help setup the delegation token 
integration tests. Since it might make this PR much more complicated, I think 
we can create another JIRA ticket to track this integration task, so that it 
won't block the current task. WDYT?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [kafka] showuon commented on pull request #13172: KAFKA-14590: Move DelegationTokenCommand to tools

2023-02-20 Thread via GitHub


showuon commented on PR #13172:
URL: https://github.com/apache/kafka/pull/13172#issuecomment-1436957769

   > > @tinaselenge , thanks for the PR. Some questions:
   > > 
   > > 1. This PR creates a new `DelegationTokenCommand` class, but there's no 
old `DelegationTokenCommand` class removal. Why is that?
   > > 2. The original `DelegationTokenCommandTest` is an integration test, but 
now we changed to unit test by mockAdminClient, why do we change that?
   > > 
   > > Thanks.
   > 
   > Hi @showuon
   > 
   > 1. I have removed the existing Scala class and its test.
   > 
   > 2. I thought it's good enough to test it using the mock as it's not 
really doing anything specific with the cluster. I understand that changes the 
test behaviour. If you think we should test the tool against an integration 
test cluster, I'm happy to change it back. Please let me know.
   
   For (1), thanks for the update
   For (2), yes, I think the integration test is important, especially after 
KRaft starting to support delegation token, we should rely on integration tests 
to make sure everything works fine on both ZK and KRaft mode. But the mock 
client implementation are also great to be added. Those could also be kept. 
   
   Thank you.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org