[jira] [Comment Edited] (KAFKA-6964) Add ability to print all internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523810#comment-16523810 ] Jagadesh Adireddi edited comment on KAFKA-6964 at 6/26/18 2:38 PM: ---

[jira] [Commented] (KAFKA-7028) super.users doesn't work with custom principals

[ https://issues.apache.org/jira/browse/KAFKA-7028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523839#comment-16523839 ] Stanislav Kozlovski commented on KAFKA-7028: After investigation, me and [~rsivaram] found

[jira] [Commented] (KAFKA-6964) Add ability to print all internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523853#comment-16523853 ] Bill Bejeck commented on KAFKA-6964: [~jadireddi]  I was thinking along the lines of printing the

[jira] [Commented] (KAFKA-6812) Async ConsoleProducer exits with 0 status even after data loss

[ https://issues.apache.org/jira/browse/KAFKA-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523867#comment-16523867 ] Stanislav Kozlovski commented on KAFKA-6812: I believe this current behavior is correct. You

[jira] [Resolved] (KAFKA-7100) kafka.tools.GetOffsetShell with enable Kerberos Security on Kafka1.0

[ https://issues.apache.org/jira/browse/KAFKA-7100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7100. -- Resolution: Duplicate This is being tracked in KAFKA-5235. > kafka.tools.GetOffsetShell with enable

[jira] [Commented] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523836#comment-16523836 ] Bastien Bussy commented on KAFKA-7099: -- Hello, I am a colleague of Vincent. *Disclaimer* : we work

[jira] [Updated] (KAFKA-7093) Kafka warn messages after upgrade from 0.11.0.1 to 1.1.0

[ https://issues.apache.org/jira/browse/KAFKA-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suleyman updated KAFKA-7093: Issue Type: Bug (was: New Feature) > Kafka warn messages after upgrade from 0.11.0.1 to 1.1.0 >

[jira] [Commented] (KAFKA-6964) Add ability to print all internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523810#comment-16523810 ] Jagadesh Adireddi commented on KAFKA-6964: -- [~mjsax],  After revisiting code, got 2 points in

[jira] [Comment Edited] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523849#comment-16523849 ] Manikumar edited comment on KAFKA-7099 at 6/26/18 3:10 PM: --- Existing issue:  

[jira] [Issue Comment Deleted] (KAFKA-6964) Add ability to print all internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-6964: --- Comment: was deleted (was: I did not double-check the code, but in general it is ok to use

[jira] [Commented] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523885#comment-16523885 ] Stanislav Kozlovski commented on KAFKA-6809: Changing them to the first approach (count both

[jira] [Commented] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523905#comment-16523905 ] Ismael Juma commented on KAFKA-6809: [~enether], these metrics exist on a per selector basis. The

[jira] [Commented] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

[ https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523849#comment-16523849 ] Manikumar commented on KAFKA-7099: -- Existing issue:  KAFKA-6415. This temporarily handled in  KAFKA-6415 

[jira] [Created] (KAFKA-7100) kafka.tools.GetOffsetShell with enable Kerberos Security on Kafka1.0

abdullah toraman created KAFKA-7100: --- Summary: kafka.tools.GetOffsetShell with enable Kerberos Security on Kafka1.0 Key: KAFKA-7100 URL: https://issues.apache.org/jira/browse/KAFKA-7100

[jira] [Updated] (KAFKA-7091) AdminClient should handle FindCoordinatorResponse errors

[ https://issues.apache.org/jira/browse/KAFKA-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-7091: - Fix Version/s: (was: 2.0.0) 2.0.1 > AdminClient should handle

[jira] [Commented] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523970#comment-16523970 ] ASF GitHub Bot commented on KAFKA-6949: --- lindong28 closed pull request #5293: KAFKA-6949;

[jira] [Assigned] (KAFKA-6268) Tools should now swallow exceptions like resolving network names

[ https://issues.apache.org/jira/browse/KAFKA-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram reassigned KAFKA-6268: - Assignee: Stanislav Kozlovski Fix Version/s: 2.1.0 > Tools should now swallow

[jira] [Commented] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523985#comment-16523985 ] Stanislav Kozlovski commented on KAFKA-6809: I'm not sure I understand what the appropriate

[jira] [Commented] (KAFKA-6964) Add ability to print all internal topic names

[ https://issues.apache.org/jira/browse/KAFKA-6964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524058#comment-16524058 ] Jagadesh Adireddi commented on KAFKA-6964: -- Got it [~bbejeck]... Should we skip this feature for

[jira] [Commented] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524117#comment-16524117 ] Vahid Hashemian commented on KAFKA-7026: [~steven.aerts] is correct. The issue reported in this

[jira] [Created] (KAFKA-7105) Refactor RocksDBSegmentsBatchingRestoreCallback and RocksDBBatchingRestoreCallback into a single class

Liquan Pei created KAFKA-7105: - Summary: Refactor RocksDBSegmentsBatchingRestoreCallback and RocksDBBatchingRestoreCallback into a single class Key: KAFKA-7105 URL: https://issues.apache.org/jira/browse/KAFKA-7105

[jira] [Commented] (KAFKA-6788) Grouping consumer requests per consumer coordinator in admin client

[ https://issues.apache.org/jira/browse/KAFKA-6788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524049#comment-16524049 ] Shun Guan commented on KAFKA-6788: -- Is this story closed? I see there are code commits and pr but

[jira] [Commented] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524060#comment-16524060 ] Ismael Juma commented on KAFKA-6809: Yes. > connections-created metric does not behave as expected >

[jira] [Created] (KAFKA-7102) Error in fetch kafka.server.ReplicaFetcherThread$FetchRequest@10c8df20

sankar created KAFKA-7102: - Summary: Error in fetch kafka.server.ReplicaFetcherThread$FetchRequest@10c8df20 Key: KAFKA-7102 URL: https://issues.apache.org/jira/browse/KAFKA-7102 Project: Kafka

[jira] [Created] (KAFKA-7104) ReplicaFetcher thread may die because of inconsistent log start offset in fetch response

Anna Povzner created KAFKA-7104: --- Summary: ReplicaFetcher thread may die because of inconsistent log start offset in fetch response Key: KAFKA-7104 URL: https://issues.apache.org/jira/browse/KAFKA-7104

[jira] [Commented] (KAFKA-6812) Async ConsoleProducer exits with 0 status even after data loss

[ https://issues.apache.org/jira/browse/KAFKA-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524080#comment-16524080 ] Andras Beni commented on KAFKA-6812: [~enether] In sync mode, when an exception occurs, it is

[jira] [Created] (KAFKA-7103) Use bulkloading for RocksDBSegmentedBytesStore during init

Liquan Pei created KAFKA-7103: - Summary: Use bulkloading for RocksDBSegmentedBytesStore during init Key: KAFKA-7103 URL: https://issues.apache.org/jira/browse/KAFKA-7103 Project: Kafka Issue

[jira] [Commented] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523295#comment-16523295 ] ASF GitHub Bot commented on KAFKA-6949: --- lindong28 opened a new pull request #5293: KAFKA-6949;

[jira] [Commented] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523297#comment-16523297 ] Dong Lin commented on KAFKA-6949: - [~rsivaram] The patch has been merged into trunk. I opened PR

[jira] [Updated] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram updated KAFKA-6949: -- [~lindong] You can cherry-pick and push the commit to 2.0 branch without a PR or further reviews

[jira] [Commented] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523343#comment-16523343 ] Odin Standal commented on KAFKA-6817: - Would it be possible to change transactional.id.expiration.ms

[jira] [Commented] (KAFKA-6944) Add system tests testing the new throttling behavior using older clients/brokers

[ https://issues.apache.org/jira/browse/KAFKA-6944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523348#comment-16523348 ] ASF GitHub Bot commented on KAFKA-6944: --- jonlee2 opened a new pull request #5294: KAFKA-6944: Add

[jira] [Commented] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523292#comment-16523292 ] ASF GitHub Bot commented on KAFKA-6949: --- lindong28 closed pull request #5081: KAFKA-6949;

[jira] [Updated] (KAFKA-6949) alterReplicaLogDirs() should grab partition lock when accessing log of the future replica

[ https://issues.apache.org/jira/browse/KAFKA-6949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin updated KAFKA-6949: Fix Version/s: 2.0.0 > alterReplicaLogDirs() should grab partition lock when accessing log of the >

[jira] [Commented] (KAFKA-7012) Performance issue upgrading to kafka 1.0.1 or 1.1

[ https://issues.apache.org/jira/browse/KAFKA-7012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523303#comment-16523303 ] Dong Lin commented on KAFKA-7012: - Great to know that the fix works!   > Performance issue upgrading to

[jira] [Resolved] (KAFKA-2488) System tests: updated console_consumer.py to support new consumer

[ https://issues.apache.org/jira/browse/KAFKA-2488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2488. -- Resolution: Fixed Support was added in > 0.10.1 Kafka versions. > System tests: updated

[jira] [Commented] (KAFKA-7095) Low traffic consumer is not consuming messages after the offsets is deleted by Kafka

[ https://issues.apache.org/jira/browse/KAFKA-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523439#comment-16523439 ] Aldo Sinanaj commented on KAFKA-7095: - Hi [~hachikuji] thanks for replying. The consumer

[jira] [Resolved] (KAFKA-2215) Improve Randomness for ConsoleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-2215. -- Resolution: Not A Problem Closing inactive issue. Also the default for console consumer's

[jira] [Comment Edited] (KAFKA-7095) Low traffic consumer is not consuming messages after the offsets is deleted by Kafka

[ https://issues.apache.org/jira/browse/KAFKA-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523439#comment-16523439 ] Aldo Sinanaj edited comment on KAFKA-7095 at 6/26/18 12:06 PM: --- Hi

[jira] [Comment Edited] (KAFKA-7095) Low traffic consumer is not consuming messages after the offsets is deleted by Kafka

[ https://issues.apache.org/jira/browse/KAFKA-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523439#comment-16523439 ] Aldo Sinanaj edited comment on KAFKA-7095 at 6/26/18 12:26 PM: --- Hi

[jira] [Commented] (KAFKA-7095) Low traffic consumer is not consuming messages after the offsets is deleted by Kafka

[ https://issues.apache.org/jira/browse/KAFKA-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524432#comment-16524432 ] Jason Gustafson commented on KAFKA-7095: The easy thing to do is increase the

[jira] [Commented] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524543#comment-16524543 ] Narayan Periwal commented on KAFKA-7026: [~vahid], unfortunately we are not able to reproduce

[jira] [Commented] (KAFKA-5037) Infinite loop if all input topics are unknown at startup

[ https://issues.apache.org/jira/browse/KAFKA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524421#comment-16524421 ] Guozhang Wang commented on KAFKA-5037: -- If we want to only fix-forward this issue beyond 2.0. I'd

[jira] [Commented] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524517#comment-16524517 ] Narayan Periwal commented on KAFKA-7026: [~vahid], Agree that this may not be the actual cause of

[jira] [Commented] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524538#comment-16524538 ] Vahid Hashemian commented on KAFKA-7026: [~nperiwal] Is the issue you described reproducible by

[jira] [Comment Edited] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524543#comment-16524543 ] Narayan Periwal edited comment on KAFKA-7026 at 6/27/18 4:10 AM: -

[jira] [Comment Edited] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524543#comment-16524543 ] Narayan Periwal edited comment on KAFKA-7026 at 6/27/18 4:11 AM: -

[jira] [Commented] (KAFKA-6587) Kafka Streams hangs when not able to access internal topics

[ https://issues.apache.org/jira/browse/KAFKA-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524306#comment-16524306 ] Guozhang Wang commented on KAFKA-6587: -- I looked into the source code, and I believe this issue

[jira] [Commented] (KAFKA-6437) Streams does not warn about missing input topics, but hangs

[ https://issues.apache.org/jira/browse/KAFKA-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524379#comment-16524379 ] Guozhang Wang commented on KAFKA-6437: -- I think this is again correlated to

[jira] [Commented] (KAFKA-7101) Session Window store should set topic policy `compact,cleanup`

[ https://issues.apache.org/jira/browse/KAFKA-7101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524222#comment-16524222 ] ASF GitHub Bot commented on KAFKA-7101: --- guozhangwang opened a new pull request #5298: KAFKA-7101:

[jira] [Commented] (KAFKA-6520) When a Kafka Stream can't communicate with the server, it's Status stays RUNNING

[ https://issues.apache.org/jira/browse/KAFKA-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524331#comment-16524331 ] Guozhang Wang commented on KAFKA-6520: -- Hi [~milindjain], are you still working on this ticket? >

[jira] [Updated] (KAFKA-7104) ReplicaFetcher thread may die because of inconsistent log start offset in fetch response

[ https://issues.apache.org/jira/browse/KAFKA-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Povzner updated KAFKA-7104: Description: What we saw: The follower fetches offset 116617, which it was able successfully

[jira] [Commented] (KAFKA-5037) Infinite loop if all input topics are unknown at startup

[ https://issues.apache.org/jira/browse/KAFKA-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524389#comment-16524389 ] Guozhang Wang commented on KAFKA-5037: -- I'm now grouping these three tickets: 5037, 6587 and 6437

[jira] [Created] (KAFKA-7106) Remove segment/segmentInterval from Window definition

John Roesler created KAFKA-7106: --- Summary: Remove segment/segmentInterval from Window definition Key: KAFKA-7106 URL: https://issues.apache.org/jira/browse/KAFKA-7106 Project: Kafka Issue

[jira] [Updated] (KAFKA-7104) ReplicaFetcher thread may die because of inconsistent log start offset in fetch response

[ https://issues.apache.org/jira/browse/KAFKA-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Povzner updated KAFKA-7104: Description: What we saw: The follower fetches offset 116617, which it was able successfully

[jira] [Created] (KAFKA-7099) KafkaLog4jAppender - not sending any message with level DEBUG

Vincent Lebreil created KAFKA-7099: -- Summary: KafkaLog4jAppender - not sending any message with level DEBUG Key: KAFKA-7099 URL: https://issues.apache.org/jira/browse/KAFKA-7099 Project: Kafka

[jira] [Commented] (KAFKA-7088) Kafka streams thread waits infinitely on transaction init

[ https://issues.apache.org/jira/browse/KAFKA-7088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523725#comment-16523725 ] Lukasz Gluchowski commented on KAFKA-7088: -- Sorry but DEBUG is still to verbose. It is impacting

[jira] [Updated] (KAFKA-7106) Remove segment/segmentInterval from Window definition

[ https://issues.apache.org/jira/browse/KAFKA-7106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7106: --- Labels: needs-kip (was: ) > Remove segment/segmentInterval from Window definition >

[jira] [Updated] (KAFKA-7107) Ability to configure state store for JoinWindows in KStream-KStream join

[ https://issues.apache.org/jira/browse/KAFKA-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-7107: --- Labels: needs-kip (was: ) > Ability to configure state store for JoinWindows in

[jira] [Created] (KAFKA-7107) Ability to configure state store for JoinWindows in KStream-KStream join

John Roesler created KAFKA-7107: --- Summary: Ability to configure state store for JoinWindows in KStream-KStream join Key: KAFKA-7107 URL: https://issues.apache.org/jira/browse/KAFKA-7107 Project: Kafka

[jira] [Assigned] (KAFKA-6809) connections-created metric does not behave as expected

[ https://issues.apache.org/jira/browse/KAFKA-6809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanislav Kozlovski reassigned KAFKA-6809: -- Assignee: Stanislav Kozlovski > connections-created metric does not behave as

[jira] [Commented] (KAFKA-7026) Sticky assignor could assign a partition to multiple consumers

[ https://issues.apache.org/jira/browse/KAFKA-7026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523582#comment-16523582 ] Steven Aerts commented on KAFKA-7026: - [~nperiwal] looking at the code of the {{RangeAssignor}}, I do

[jira] [Resolved] (KAFKA-5080) Convert ProducerBounceTest to use the new KafkaConsumer

[ https://issues.apache.org/jira/browse/KAFKA-5080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5080. -- Resolution: Fixed ProducerBounceTest is removed as part of old consumer changes. > Convert

[jira] [Resolved] (KAFKA-5079) ProducerBounceTest fails occasionally with a SocketTimeoutException

[ https://issues.apache.org/jira/browse/KAFKA-5079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-5079. -- Resolution: Fixed ProducerBounceTest is removed as part old consumer changes. > ProducerBounceTest

[jira] [Commented] (KAFKA-6211) PartitionAssignmentState is protected whereas KafkaConsumerGroupService.describeGroup() returns PartitionAssignmentState Object

[ https://issues.apache.org/jira/browse/KAFKA-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523616#comment-16523616 ] Manikumar commented on KAFKA-6211: -- ConsumerGroupCommand internal classes/methods are not public API.

[jira] [Comment Edited] (KAFKA-6211) PartitionAssignmentState is protected whereas KafkaConsumerGroupService.describeGroup() returns PartitionAssignmentState Object

[ https://issues.apache.org/jira/browse/KAFKA-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523616#comment-16523616 ] Manikumar edited comment on KAFKA-6211 at 6/26/18 11:56 AM:

[jira] [Commented] (KAFKA-4513) Support migration of old consumers to new consumers without downtime

[ https://issues.apache.org/jira/browse/KAFKA-4513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523625#comment-16523625 ] Manikumar commented on KAFKA-4513: -- [~ijuma] Can we close this JIRA? > Support migration of old