[
https://issues.apache.org/jira/browse/KAFKA-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470385#comment-17470385
]
kaushik srinivas edited comment on KAFKA-13578 at 1/7/22, 7:25 AM:
---
[
https://issues.apache.org/jira/browse/KAFKA-13578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470385#comment-17470385
]
kaushik srinivas commented on KAFKA-13578:
--
[~ijuma]
Can you provide some ins
kaushik srinivas created KAFKA-13578:
Summary: Need clarity on the bridge release version of kafka
without zookeeper in the eco system - KIP500
Key: KAFKA-13578
URL: https://issues.apache.org/jira/browse/KAFKA
[
https://issues.apache.org/jira/browse/KAFKA-12616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470362#comment-17470362
]
dengziming commented on KAFKA-12616:
It seems we can use QuorumTestHarness to test b
dengziming commented on a change in pull request #11634:
URL: https://github.com/apache/kafka/pull/11634#discussion_r780047401
##
File path:
core/src/test/scala/unit/kafka/admin/TopicCommandIntegrationTest.scala
##
@@ -443,25 +486,30 @@ class TopicCommandIntegrationTest extend
ahmed3465 edited a comment on pull request #6097:
URL: https://github.com/apache/kafka/pull/6097#issuecomment-1007159144
Is there a way I can alter the code and share the Mbean sensor across
multiple consumers using the same client-id ?
We have an auto-scaling Kafka connect cluster which
ahmed3465 edited a comment on pull request #6097:
URL: https://github.com/apache/kafka/pull/6097#issuecomment-1007159144
Is there a way to share the Mbean sensor across multiple consumers using the
same client-id ?
We have an auto-scaling Kafka connect cluster which uses client and user
ahmed3465 commented on pull request #6097:
URL: https://github.com/apache/kafka/pull/6097#issuecomment-1007159144
Is there a way to share the Mbean sensor across multiple consumers using the
same client-id ?
We have an auto-scaling Kafka connect cluster which uses client and user
quotas
Abhijit-Mane closed pull request #10782:
URL: https://github.com/apache/kafka/pull/10782
--
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-unsu
Abhijit-Mane commented on pull request #10782:
URL: https://github.com/apache/kafka/pull/10782#issuecomment-1007150259
Closing issue, details in https://issues.apache.org/jira/browse/KAFKA-12847
--
This is an automated message from the Apache Git Service.
To respond to the message, please
dengziming commented on pull request #11655:
URL: https://github.com/apache/kafka/pull/11655#issuecomment-1007141611
Hello @cmccabe , Please help review this, thank you.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
dengziming opened a new pull request #11655:
URL: https://github.com/apache/kafka/pull/11655
*More detailed description of your change*
This PR follows #11629 to enable `CreateTopicsRequestWithForwardingTest` and
`CreateTopicsRequestWithPolicyTest` in KRaft mode.
*Summary of testi
cmccabe merged pull request #11633:
URL: https://github.com/apache/kafka/pull/11633
--
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.
cmccabe commented on pull request #11633:
URL: https://github.com/apache/kafka/pull/11633#issuecomment-1006993814
Thanks for the review, @jsancio !
> LGTM @cmccabe . Should we always provide a description for the commit? If
so, can you please include a description?
I think thi
cmccabe commented on pull request #11634:
URL: https://github.com/apache/kafka/pull/11634#issuecomment-1006991927
I fixed some pre-existing race conditions in the tests, related to metadata
propagation.
--
This is an automated message from the Apache Git Service.
To respond to the messag
cmccabe commented on pull request #11640:
URL: https://github.com/apache/kafka/pull/11640#issuecomment-1006980868
Test failures are not related. They are
`kafka.controller.ControllerIntegrationTest.testTopicIdCreatedOnUpgrade` (a
test for the old controller), and
`EosIntegrationTest.shoul
cmccabe edited a comment on pull request #11639:
URL: https://github.com/apache/kafka/pull/11639#issuecomment-1006976419
Weird error from Jenkins:
```
[2022-01-02T08:54:28.118Z] The recommended git tool is: git
Resume after a restart not supported for non-blocking synchronou
cmccabe commented on pull request #11639:
URL: https://github.com/apache/kafka/pull/11639#issuecomment-1006976419
Weird error from Jenkins:
```
[2022-01-02T08:54:28.118Z] The recommended git tool is: git
Resume after a restart not supported for non-blocking synchronous steps
cmccabe commented on pull request #11638:
URL: https://github.com/apache/kafka/pull/11638#issuecomment-1006975655
Rebased
--
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.
T
cmccabe commented on pull request #11636:
URL: https://github.com/apache/kafka/pull/11636#issuecomment-1006967605
Rebased
--
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.
T
cmccabe merged pull request #11635:
URL: https://github.com/apache/kafka/pull/11635
--
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.
cmccabe commented on pull request #11635:
URL: https://github.com/apache/kafka/pull/11635#issuecomment-1006965338
Thanks for the review, @jsancio .
> LGTM @cmccabe . Should we always provide a description for the commit? If
so, can you please include a description?
If the desc
ewencp commented on pull request #10056:
URL: https://github.com/apache/kafka/pull/10056#issuecomment-1006954861
@mdshadabin as mentioned by @ijuma above, this hasn't been backported to
older releases yet. Unit tests are sometimes flaky, so might just be due to
that. At this point it would
ccding commented on pull request #11345:
URL: https://github.com/apache/kafka/pull/11345#issuecomment-1006930874
ping @kowshik @junrao @hachikuji
--
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
diegoazevedo commented on pull request #7898:
URL: https://github.com/apache/kafka/pull/7898#issuecomment-1006920498
Just for information, the use of an obsolete version of log4j is now seen as
a critical vulnerability for some security scanners. We received this "Critical
Warning" from Te
vbsiegem commented on pull request #7898:
URL: https://github.com/apache/kafka/pull/7898#issuecomment-1006913721
Are there any firm plans at this time for when log4j v2 support in Kafka
will be released, and in what release(s)?
--
This is an automated message from the Apache Git Service.
guozhangwang merged pull request #11652:
URL: https://github.com/apache/kafka/pull/11652
--
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-unsu
cmccabe merged pull request #11593:
URL: https://github.com/apache/kafka/pull/11593
--
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.
cmccabe commented on pull request #11593:
URL: https://github.com/apache/kafka/pull/11593#issuecomment-1006801028
> Should we add an integration that shows the expected behavior on the
broker side?
It would be a difficult integration test to write, since the existing test
framework
cmccabe merged pull request #11629:
URL: https://github.com/apache/kafka/pull/11629
--
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.
cmccabe commented on pull request #11629:
URL: https://github.com/apache/kafka/pull/11629#issuecomment-1006797056
Test failures are not related. Comitting.
--
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
cmccabe commented on pull request #11629:
URL: https://github.com/apache/kafka/pull/11629#issuecomment-1006796926
Thanks @hachikuji. Thanks @dengziming for finding a race condition in the
test, which is fixed now!
--
This is an automated message from the Apache Git Service.
To respond to
cmccabe commented on a change in pull request #11629:
URL: https://github.com/apache/kafka/pull/11629#discussion_r779746531
##
File path:
core/src/test/scala/unit/kafka/server/AbstractCreateTopicsRequestTest.scala
##
@@ -136,11 +144,13 @@ abstract class AbstractCreateTopicsReq
vamossagar12 commented on pull request #11211:
URL: https://github.com/apache/kafka/pull/11211#issuecomment-1006768109
> > @mjsax @ableegoldman could you chime in here?
>
> @guozhangwang could we also decide upon the next steps here?
@guozhangwang / @ableegoldman any suggestio
vamossagar12 commented on a change in pull request #11433:
URL: https://github.com/apache/kafka/pull/11433#discussion_r779716364
##
File path:
streams/src/main/java/org/apache/kafka/streams/processor/internals/TaskManager.java
##
@@ -292,12 +327,20 @@ public void handleAssignm
vamossagar12 commented on pull request #11424:
URL: https://github.com/apache/kafka/pull/11424#issuecomment-1006767050
> hey @guozhangwang , For `CACHE_MAX_BYTES_BUFFERING_CONFIG` , I can replace
but as per one of the comments here => [#11424
(comment)](https://github.com/apache/kafka/pull
ispringer commented on a change in pull request #7898:
URL: https://github.com/apache/kafka/pull/7898#discussion_r779703586
##
File path: gradle/dependencies.gradle
##
@@ -75,6 +75,7 @@ versions += [
jmh: "1.32",
hamcrest: "2.2",
log4j: "1.2.17",
+ log4j2: "2.17.0",
tyamashi-oss commented on pull request #10644:
URL: https://github.com/apache/kafka/pull/10644#issuecomment-1006638780
I'm having a similar problem. I was looking for a solution to my problem and
found here. Please forgive me for expressing my personal opinion and sharing my
similar proble
gurinderu closed pull request #11654:
URL: https://github.com/apache/kafka/pull/11654
--
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-unsubsc
gurinderu opened a new pull request #11654:
URL: https://github.com/apache/kafka/pull/11654
This fix is a copy-paste from https://github.com/apache/kafka/pull/8066
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
[
https://issues.apache.org/jira/browse/KAFKA-13577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison reassigned KAFKA-13577:
--
Assignee: Mickael Maison
> Replace EasyMock and PowerMock with Mockito in core module
Mickael Maison created KAFKA-13577:
--
Summary: Replace EasyMock and PowerMock with Mockito in core module
Key: KAFKA-13577
URL: https://issues.apache.org/jira/browse/KAFKA-13577
Project: Kafka
rajinisivaram merged pull request #11653:
URL: https://github.com/apache/kafka/pull/11653
--
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-uns
dengziming commented on a change in pull request #11629:
URL: https://github.com/apache/kafka/pull/11629#discussion_r779380315
##
File path:
core/src/test/scala/unit/kafka/server/AbstractCreateTopicsRequestTest.scala
##
@@ -136,11 +144,13 @@ abstract class AbstractCreateTopics
44 matches
Mail list logo
