[
https://issues.apache.org/jira/browse/KAFKA-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794176#comment-16794176
]
Manikumar commented on KAFKA-7898:
--
[~steven-usabilla] I think it is good to have fix in 2.1 branch as
[
https://issues.apache.org/jira/browse/KAFKA-7801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7801.
--
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request 6109
[
https://issues.apache.org/jira/browse/KAFKA-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7939.
--
Resolution: Fixed
Issue resolved by pull request 6418
[https://github.com/apache/kafka/pull/6418]
>
[
https://issues.apache.org/jira/browse/KAFKA-7922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7922.
--
Resolution: Fixed
Fix Version/s: 2.3.0
> Returned authorized operations in describe responses
[
https://issues.apache.org/jira/browse/KAFKA-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-8060.
--
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request 6387
[
https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-8061:
-
Summary: Handle concurrent ProducerId reset and call to Sender thread
shutdown (was: Handle concurrent
[
https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-8061:
-
Summary: Handle concurrent ProducerId reset while closing Sender thread.
(was: Handle ProducerId reset
[
https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-8061:
-
Summary: Handle ProducerId reset while closing Sender thread. (was: Use
forceClose flag to check in the
[
https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-8061:
-
Description:
In KAFKA-5503, we have added a check
(https://github.com/apache/kafka/pull/5881) for
[
https://issues.apache.org/jira/browse/KAFKA-8061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-8061:
-
Description:
In KAFKA-5503, we have added a check
(https://github.com/apache/kafka/pull/5881) for
[
https://issues.apache.org/jira/browse/KAFKA-8018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-8018.
--
Resolution: Fixed
> Flaky Test
>
[
https://issues.apache.org/jira/browse/KAFKA-8044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786563#comment-16786563
]
Manikumar commented on KAFKA-8044:
--
Underlying issue for this test failure is KAFKA-8061. As I have seen
Manikumar created KAFKA-8061:
Summary: Use forceClose flag to check in the loop inside
maybeWaitForProducerId.
Key: KAFKA-8061
URL: https://issues.apache.org/jira/browse/KAFKA-8061
Project: Kafka
Manikumar created KAFKA-8044:
Summary: System Test Failure:
ReassignPartitionsTest.test_reassign_partitions
Key: KAFKA-8044
URL: https://issues.apache.org/jira/browse/KAFKA-8044
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7312:
-
Fix Version/s: (was: 2.2.0)
2.2.1
2.3.0
> Transient failure in
[
https://issues.apache.org/jira/browse/KAFKA-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7651.
--
Resolution: Fixed
Fix Version/s: 2.2.1
2.1.2
2.0.2
This
[
https://issues.apache.org/jira/browse/KAFKA-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7312.
--
Resolution: Fixed
Fix Version/s: (was: 2.3.0)
2.1.2
[
https://issues.apache.org/jira/browse/KAFKA-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782757#comment-16782757
]
Manikumar commented on KAFKA-8030:
--
cc [~viktorsomogyi]
> Flaky Test
>
[
https://issues.apache.org/jira/browse/KAFKA-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7997.
--
Resolution: Fixed
Fix Version/s: 2.3.0
Issue resolved by pull request 6324
[
https://issues.apache.org/jira/browse/KAFKA-7925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16781349#comment-16781349
]
Manikumar commented on KAFKA-7925:
--
You can use below steps to checkout the PR.
{quote}git clone
[
https://issues.apache.org/jira/browse/KAFKA-7832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7832.
--
Resolution: Fixed
Fix Version/s: 2.3.0
> Use automatic RPC generation in CreateTopics
>
[
https://issues.apache.org/jira/browse/KAFKA-7972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7972.
--
Resolution: Fixed
Fix Version/s: 2.3.0
> Replace SaslHandshake request/response with automated
[
https://issues.apache.org/jira/browse/KAFKA-7982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776537#comment-16776537
]
Manikumar commented on KAFKA-7982:
--
[~xabhi] Can you give us more details about deployment and Jaas
[
https://issues.apache.org/jira/browse/KAFKA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7799.
--
Resolution: Fixed
Fix Version/s: 2.3.0
> Fix flaky test RestServerTest.testCORSEnabled
>
[
https://issues.apache.org/jira/browse/KAFKA-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7896.
--
Resolution: Fixed
Fix Version/s: 2.3.0
> Add some Log4J Kafka Properties for Producing to
[
https://issues.apache.org/jira/browse/KAFKA-7799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reopened KAFKA-7799:
--
This test is failing frequently on Jenkins builds. Reopening.
> Fix flaky test
[
https://issues.apache.org/jira/browse/KAFKA-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7466:
Assignee: Manikumar
> Implement KIP-339: Create a new IncrementalAlterConfigs API
>
[
https://issues.apache.org/jira/browse/KAFKA-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7781.
--
Resolution: Fixed
Assignee: Kamal Chandraprakash
Fix Version/s: 2.2.0
> Add validation
[
https://issues.apache.org/jira/browse/KAFKA-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5994:
Assignee: Manikumar
> Improve transparency of broker user ACL misconfigurations
>
[
https://issues.apache.org/jira/browse/KAFKA-5994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5994.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 5021
[
https://issues.apache.org/jira/browse/KAFKA-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7752.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 6072
[
https://issues.apache.org/jira/browse/KAFKA-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7054:
Assignee: Manohar Vanam
> Kafka describe command should throw topic doesn't exist exception.
>
[
https://issues.apache.org/jira/browse/KAFKA-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7054.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 5211
[
https://issues.apache.org/jira/browse/KAFKA-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7762:
Assignee: Matthias Weßendorf
> KafkaConsumer uses old API in the javadocs
>
[
https://issues.apache.org/jira/browse/KAFKA-7762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7762.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 6052
[
https://issues.apache.org/jira/browse/KAFKA-7742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7742.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 6037
[
https://issues.apache.org/jira/browse/KAFKA-7746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16723750#comment-16723750
]
Manikumar commented on KAFKA-7746:
--
Can you try below format?
{code}
bin/kafka-configs.sh
[
https://issues.apache.org/jira/browse/KAFKA-7696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708257#comment-16708257
]
Manikumar commented on KAFKA-7696:
--
[~asasvari] This is related to KAFKA-4493. There is a WIP PR
Manikumar created KAFKA-7694:
Summary: Support ZooKeeper based master/secret key management for
delegation tokens
Key: KAFKA-7694
URL: https://issues.apache.org/jira/browse/KAFKA-7694
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706140#comment-16706140
]
Manikumar commented on KAFKA-7390:
--
cc [~ijuma]
> Enable the find-sec-bugs spotBugs plugin for Gradle
>
[
https://issues.apache.org/jira/browse/KAFKA-7617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7617.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 5906
[
https://issues.apache.org/jira/browse/KAFKA-7259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7259.
--
Resolution: Fixed
Issue resolved by pull request 5480
[https://github.com/apache/kafka/pull/5480]
>
[
https://issues.apache.org/jira/browse/KAFKA-6149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6149.
--
Resolution: Fixed
Fix Version/s: 0.11.0.1
1.0.0
This was fixed in 1.0 and
[
https://issues.apache.org/jira/browse/KAFKA-7205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7205:
-
Labels: needs-kip (was: )
Yes, you can raise PR against trunk. Since this is a public API change, we
[
https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16694262#comment-16694262
]
Manikumar commented on KAFKA-7390:
--
[~timmy2702] I have given you Jira contributor permissions. Please
[
https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7390:
Assignee: (was: Manikumar)
> Enable the find-sec-bugs spotBugs plugin for Gradle
>
[
https://issues.apache.org/jira/browse/KAFKA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7390:
Assignee: Manikumar
> Enable the find-sec-bugs spotBugs plugin for Gradle
>
[
https://issues.apache.org/jira/browse/KAFKA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-6971.
--
Resolution: Duplicate
> Passing in help flag to kafka-console-producer should print arg options
>
[
https://issues.apache.org/jira/browse/KAFKA-7616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7616.
--
Resolution: Fixed
Fix Version/s: 2.2.0
Issue resolved by pull request 5901
[
https://issues.apache.org/jira/browse/KAFKA-7659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7659.
--
Resolution: Invalid
> dummy test
> --
>
> Key: KAFKA-7659
>
[
https://issues.apache.org/jira/browse/KAFKA-764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-764.
-
Resolution: Duplicate
This old issue is similar to KAFKA-7165. Closing this as duplicate KAFKA-7165
>
[
https://issues.apache.org/jira/browse/KAFKA-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16692035#comment-16692035
]
Manikumar commented on KAFKA-7361:
--
This must be fixed in
[
https://issues.apache.org/jira/browse/KAFKA-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7323.
--
Resolution: Not A Problem
Closing as per above comment. probably heap memory is not sufficient.
[
https://issues.apache.org/jira/browse/KAFKA-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7554.
--
Resolution: Not A Problem
Default Zookeeper session timeout value 6 seconds. If the server fails to
[
https://issues.apache.org/jira/browse/KAFKA-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681900#comment-16681900
]
Manikumar commented on KAFKA-6584:
--
[~pachilo] Yes
> Session expiration concurrent with ZooKeeper
[
https://issues.apache.org/jira/browse/KAFKA-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681872#comment-16681872
]
Manikumar commented on KAFKA-6584:
--
[~pachilo] maybe we can leave this as open, so that we can track
[
https://issues.apache.org/jira/browse/KAFKA-7080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681546#comment-16681546
]
Manikumar commented on KAFKA-7080:
--
[~vvcephei] [~guozhang] Can we create a separate JIRA for the part
[
https://issues.apache.org/jira/browse/KAFKA-7286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7286:
-
Fix Version/s: 2.0.1
> Loading offsets and group metadata hangs with large group metadata records
>
[
https://issues.apache.org/jira/browse/KAFKA-7126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7126:
-
Fix Version/s: (was: 2.0.0)
2.0.1
> Reduce number of rebalance for large consumer
[
https://issues.apache.org/jira/browse/KAFKA-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7313:
-
Fix Version/s: (was: 2.0.1)
2.0.2
> StopReplicaRequest should attempt to remove
[
https://issues.apache.org/jira/browse/KAFKA-7559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7559:
-
Fix Version/s: (was: 2.0.1)
2.0.2
> ConnectStandaloneFileTest system tests do not
[
https://issues.apache.org/jira/browse/KAFKA-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7561:
-
Fix Version/s: (was: 2.1.1)
2.1.0
> Console Consumer - system test fails
>
[
https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7579.
--
Resolution: Fixed
Fix Version/s: 2.1.0
This is fixed via KAFKA-7561.
> System Test Failure -
[
https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7579:
-
Priority: Major (was: Blocker)
> System Test Failure -
>
[
https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7579:
-
Fix Version/s: 2.0.2
> System Test Failure -
>
[
https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671733#comment-16671733
]
Manikumar commented on KAFKA-7579:
--
tests are passing locally after increasing console consume timeout.
[
https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671733#comment-16671733
]
Manikumar edited comment on KAFKA-7579 at 11/1/18 3:15 PM:
---
tests are passing
[
https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671607#comment-16671607
]
Manikumar commented on KAFKA-7579:
--
This issue is related to KAFKA-7561
> System Test Failure -
>
[
https://issues.apache.org/jira/browse/KAFKA-5891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5891:
Assignee: Maciej Bryński
> Cast transformation fails if record schema contains timestamp field
>
[
https://issues.apache.org/jira/browse/KAFKA-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7353:
Assignee: Kevin Lafferty
> Connect logs 'this' for anonymous inner classes
>
[
https://issues.apache.org/jira/browse/KAFKA-7301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7301:
Assignee: Joan Goyeau
> KTable to KTable join invocation does not resolve in Scala DSL
>
[
https://issues.apache.org/jira/browse/KAFKA-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7316:
Assignee: Joan Goyeau
> Use of filter method in KTable.scala may result in StackOverflowError
>
[
https://issues.apache.org/jira/browse/KAFKA-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7519:
Assignee: Bridger Howell (was: Manikumar)
> Transactional Ids Left in Pending State by
[
https://issues.apache.org/jira/browse/KAFKA-7519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7519:
Assignee: Manikumar
> Transactional Ids Left in Pending State by TransactionStateManager During
[
https://issues.apache.org/jira/browse/KAFKA-7547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16665001#comment-16665001
]
Manikumar commented on KAFKA-7547:
--
Since Kerberos ticket expiration times are typically short, repeated
[
https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7535:
-
Fix Version/s: (was: 2.0.2)
(was: 2.1.1)
2.0.1
>
[
https://issues.apache.org/jira/browse/KAFKA-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5462.
--
Resolution: Fixed
Fix Version/s: 2.2.0
> Add a configuration for users to specify a template
[
https://issues.apache.org/jira/browse/KAFKA-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663595#comment-16663595
]
Manikumar commented on KAFKA-7535:
--
As mentioned in the JIRA description, this only impacts consumer
[
https://issues.apache.org/jira/browse/KAFKA-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663494#comment-16663494
]
Manikumar commented on KAFKA-7546:
--
You can check this implementaion:
[
https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16656854#comment-16656854
]
Manikumar commented on KAFKA-7508:
--
[~sathish051] Please add Kafka and Java version details. Why is
[
https://issues.apache.org/jira/browse/KAFKA-7516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar updated KAFKA-7516:
-
Fix Version/s: (was: 2.0.1)
2.2.0
> Client (Producer and/or Consumer) crashes
[
https://issues.apache.org/jira/browse/KAFKA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16651985#comment-16651985
]
Manikumar commented on KAFKA-7508:
--
[~sathish051] Exception message shows "java.lang.OutOfMemoryError".
[
https://issues.apache.org/jira/browse/KAFKA-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638347#comment-16638347
]
Manikumar commented on KAFKA-7274:
--
[~rsivaram] Thanks for the explanation. Let me know, if we need to
[
https://issues.apache.org/jira/browse/KAFKA-7274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16638241#comment-16638241
]
Manikumar commented on KAFKA-7274:
--
[~rsivaram] As described in the JIRA, incase of static JAAS
[
https://issues.apache.org/jira/browse/KAFKA-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3601.
--
Resolution: Fixed
Closing in favour of newer releases. Please reopen if you think otherwise
> fail
[
https://issues.apache.org/jira/browse/KAFKA-7429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7429.
--
Resolution: Fixed
> Enable dynamic key/truststore update with same filename/password
>
[
https://issues.apache.org/jira/browse/KAFKA-7355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7355.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-7366. Raised a PR for KAFKA-7366.
> Topic
[
https://issues.apache.org/jira/browse/KAFKA-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16634303#comment-16634303
]
Manikumar commented on KAFKA-7463:
--
This might have fixed in KAFKA-7388.
> ConsoleProducer rejects
[
https://issues.apache.org/jira/browse/KAFKA-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5066.
--
Resolution: Fixed
> KafkaMetricsConfig properties and description notably missing from
>
[
https://issues.apache.org/jira/browse/KAFKA-3532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-3532.
--
Resolution: Duplicate
This will be fixed be part of KAFKA-5462/KIP-371
> add principal.builder.class
[
https://issues.apache.org/jira/browse/KAFKA-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-5462:
Assignee: Manikumar
> Add a configuration for users to specify a template for building a custom
[
https://issues.apache.org/jira/browse/KAFKA-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2471.
--
Resolution: Auto Closed
Closing inactive issue. Please reopen if the issue still exists in newer
[
https://issues.apache.org/jira/browse/KAFKA-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar reassigned KAFKA-7216:
Assignee: Manikumar
> Exception while running kafka-acls.sh from 1.0 env on target Kafka env with
[
https://issues.apache.org/jira/browse/KAFKA-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7425.
--
Resolution: Duplicate
will handle this as part of KAFKA-7216.
> Kafka Broker -Unable to start
>
[
https://issues.apache.org/jira/browse/KAFKA-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16622562#comment-16622562
]
Manikumar commented on KAFKA-7425:
--
looks like you have used Kafka 1.1+ release kafka-acls.sh script for
[
https://issues.apache.org/jira/browse/KAFKA-7422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16620453#comment-16620453
]
Manikumar commented on KAFKA-7422:
--
I don't see any object leak in the thread dump. I can see
[
https://issues.apache.org/jira/browse/KAFKA-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-7388.
--
Resolution: Fixed
Fix Version/s: 2.1.0
> An equal sign in a property value causes the broker to
[
https://issues.apache.org/jira/browse/KAFKA-5789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-5789.
--
Resolution: Duplicate
Resolving as duplicate of KAFKA-7320/KIP-361
> Deleted topic is recreated when
[
https://issues.apache.org/jira/browse/KAFKA-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2219.
--
Resolution: Auto Closed
Closing inactive issue. Please reopen if the issue still exists in newer
[
https://issues.apache.org/jira/browse/KAFKA-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Manikumar resolved KAFKA-2139.
--
Resolution: Duplicate
Closing this in-favor of KAFKA-4453/KIP-291.
> Add a separate controller messge
301 - 400 of 980 matches
Mail list logo