[jira] [Commented] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101244#comment-16101244 ] Ismael Juma commented on KAFKA-5501: The merged PR adds the async ZookeeperClient, but

[jira] [Reopened] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reopened KAFKA-5501: > use async zookeeper apis everywhere > --- > > Key: KAF

[jira] [Commented] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101231#comment-16101231 ] Ismael Juma commented on KAFKA-5641: The broker only processes one request at a time,

[jira] [Commented] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101230#comment-16101230 ] ASF GitHub Bot commented on KAFKA-5501: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-5501) use async zookeeper apis everywhere

[ https://issues.apache.org/jira/browse/KAFKA-5501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-5501. Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request 3427 [https://github.com/apache

[jira] [Commented] (KAFKA-4602) KIP-72 Allow putting a bound on memory consumed by Incoming requests

[ https://issues.apache.org/jira/browse/KAFKA-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101220#comment-16101220 ] ASF GitHub Bot commented on KAFKA-4602: --- Github user asfgit closed the pull request

[jira] [Updated] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5641: -- Component/s: network > Metadata request should always be allowed to send no regardless of value for > max.in.fl

[jira] [Updated] (KAFKA-5641) Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per.connection

[ https://issues.apache.org/jira/browse/KAFKA-5641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxihx updated KAFKA-5641: -- Summary: Metadata request should always be allowed to send no regardless of value for max.in.flight.requests.per

[jira] [Created] (KAFKA-5641) Metadata request should be allowed to send no regardless of value for max.in.flight.requests.per.connection

huxihx created KAFKA-5641: - Summary: Metadata request should be allowed to send no regardless of value for max.in.flight.requests.per.connection Key: KAFKA-5641 URL: https://issues.apache.org/jira/browse/KAFKA-5641

[jira] [Resolved] (KAFKA-5627) Reduce classes needed for LeaderAndIsrPartitionState and MetadataPartitionState

[ https://issues.apache.org/jira/browse/KAFKA-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin resolved KAFKA-5627. - Resolution: Fixed > Reduce classes needed for LeaderAndIsrPartitionState and > MetadataPartitionS

[jira] [Commented] (KAFKA-5627) Reduce classes needed for LeaderAndIsrPartitionState and MetadataPartitionState

[ https://issues.apache.org/jira/browse/KAFKA-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101125#comment-16101125 ] ASF GitHub Bot commented on KAFKA-5627: --- Github user asfgit closed the pull request

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101044#comment-16101044 ] Sumant Tambe commented on KAFKA-5621: - I'm unsure about the suggestion to share the sa

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101008#comment-16101008 ] ASF GitHub Bot commented on KAFKA-5634: --- GitHub user hachikuji opened a pull request

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16101000#comment-16101000 ] Ismael Juma commented on KAFKA-5621: Btw, we can avoid the double retry issue by simpl

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100986#comment-16100986 ] Jason Gustafson commented on KAFKA-5611: bq. Is the above a valid scenario? Does t

[jira] [Commented] (KAFKA-5494) Idempotent producer should not require max.in.flight.requests.per.connection=1 and acks=all

[ https://issues.apache.org/jira/browse/KAFKA-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100976#comment-16100976 ] Apurva Mehta commented on KAFKA-5494: - I created a separate JIRA to track the progress

[jira] [Updated] (KAFKA-5494) Idempotent producer should not require max.in.flight.requests.per.connection=1 and acks=all

[ https://issues.apache.org/jira/browse/KAFKA-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5494: Fix Version/s: 1.0.0 > Idempotent producer should not require > max.in.flight.requests.per.connecti

[jira] [Updated] (KAFKA-5494) Idempotent producer should not require max.in.flight.requests.per.connection=1 and acks=all

[ https://issues.apache.org/jira/browse/KAFKA-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5494: Description: Currently, the idempotent producer (and hence transactional producer) requires max.in.

[jira] [Updated] (KAFKA-5640) Look into making acks=all the default setting

[ https://issues.apache.org/jira/browse/KAFKA-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5640: Summary: Look into making acks=all the default setting (was: Look into making acks=all the default

[jira] [Created] (KAFKA-5640) Look into making acks=all the default setting.

Apurva Mehta created KAFKA-5640: --- Summary: Look into making acks=all the default setting. Key: KAFKA-5640 URL: https://issues.apache.org/jira/browse/KAFKA-5640 Project: Kafka Issue Type: Sub-t

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100946#comment-16100946 ] Apurva Mehta commented on KAFKA-5621: - I think there are a few points here: 1. What

[jira] [Updated] (KAFKA-5286) Producer should await transaction completion in close

[ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5286: Fix Version/s: (was: 0.11.0.1) 1.0.0 > Producer should await transaction comp

[jira] [Updated] (KAFKA-5286) Producer should await transaction completion in close

[ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5286: Affects Version/s: 0.11.0.0 > Producer should await transaction completion in close > --

[jira] [Commented] (KAFKA-5286) Producer should await transaction completion in close

[ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100900#comment-16100900 ] Apurva Mehta commented on KAFKA-5286: - I think that calling {{abortTransaction}} from

[jira] [Commented] (KAFKA-4628) Support KTable/GlobalKTable Joins

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100894#comment-16100894 ] Vikas Tikoo commented on KAFKA-4628: Is there a timeline for this feature? > Support

[jira] [Updated] (KAFKA-5639) Enhance DescribeGroups protocol to include additional group information

[ https://issues.apache.org/jira/browse/KAFKA-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-5639: --- Description: The [{{DescribeGroups}}|https://kafka.apache.org/protocol#The_Messages_DescribeG

[jira] [Updated] (KAFKA-5639) Enhance DescribeGroups protocol to include additional group information

[ https://issues.apache.org/jira/browse/KAFKA-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-5639: --- Description: The [{{DescribeGroups}}|https://kafka.apache.org/protocol#The_Messages_DescribeG

[jira] [Commented] (KAFKA-5630) Consumer poll loop over the same record after a CorruptRecordException

[ https://issues.apache.org/jira/browse/KAFKA-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100698#comment-16100698 ] ASF GitHub Bot commented on KAFKA-5630: --- GitHub user becketqin opened a pull request

[jira] [Created] (KAFKA-5639) Enhance DescribeGroups API to return additional group information

Vahid Hashemian created KAFKA-5639: -- Summary: Enhance DescribeGroups API to return additional group information Key: KAFKA-5639 URL: https://issues.apache.org/jira/browse/KAFKA-5639 Project: Kafka

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100535#comment-16100535 ] Jorge Quilcate commented on KAFKA-4327: --- [~mjsax] thanks! One thing is not clear t

[jira] [Updated] (KAFKA-5638) Inconsistency in consumer group related ACLs

[ https://issues.apache.org/jira/browse/KAFKA-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vahid Hashemian updated KAFKA-5638: --- Description: Users can see all groups in the cluster (using consumer group’s {{--list}}  optio

[jira] [Created] (KAFKA-5638) Inconsistency in consumer group related ACLs

Vahid Hashemian created KAFKA-5638: -- Summary: Inconsistency in consumer group related ACLs Key: KAFKA-5638 URL: https://issues.apache.org/jira/browse/KAFKA-5638 Project: Kafka Issue Type: Bu

[jira] [Commented] (KAFKA-5635) KIP-181 Kafka-Connect integrate with kafka ReST Proxy

[ https://issues.apache.org/jira/browse/KAFKA-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100399#comment-16100399 ] Ewen Cheslack-Postava commented on KAFKA-5635: -- bq. Kafka connect currently u

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100381#comment-16100381 ] Jason Gustafson commented on KAFKA-5634: I can confirm that this bug occurs when a

[jira] [Comment Edited] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100349#comment-16100349 ] Sumant Tambe edited comment on KAFKA-5621 at 7/25/17 4:55 PM: --

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100349#comment-16100349 ] Sumant Tambe commented on KAFKA-5621: - [~ijuma], [~apurva], It looks like this proposa

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100252#comment-16100252 ] Jason Gustafson commented on KAFKA-5634: I've been looking at this a bit more. I t

[jira] [Created] (KAFKA-5637) Document compatibility and release policies

Ismael Juma created KAFKA-5637: -- Summary: Document compatibility and release policies Key: KAFKA-5637 URL: https://issues.apache.org/jira/browse/KAFKA-5637 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-5636) DSL: allow sliding windows to be used directly (i.e. not just implicitly when doing joins)

Michael Noll created KAFKA-5636: --- Summary: DSL: allow sliding windows to be used directly (i.e. not just implicitly when doing joins) Key: KAFKA-5636 URL: https://issues.apache.org/jira/browse/KAFKA-5636

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100120#comment-16100120 ] Matthias J. Sax commented on KAFKA-4327: [~jeqo] I assigned this to you, as it is

[jira] [Assigned] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-4327: -- Assignee: Jorge Quilcate (was: Matthias J. Sax) > Move Reset Tool from core to streams

[jira] [Updated] (KAFKA-4914) Partition re-assignment tool should check types before persisting state in ZooKeeper

[ https://issues.apache.org/jira/browse/KAFKA-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar updated KAFKA-4914: - Fix Version/s: 1.0.0 > Partition re-assignment tool should check types before persisting state in > ZooKe

[jira] [Commented] (KAFKA-5286) Producer should await transaction completion in close

[ https://issues.apache.org/jira/browse/KAFKA-5286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100100#comment-16100100 ] Ismael Juma commented on KAFKA-5286: [~hachikuji] [~apurva], are any of you planning t

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099978#comment-16099978 ] Ismael Juma commented on KAFKA-5611: After [~hachikuji] addresses your comments, would

[jira] [Updated] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5611: --- Fix Version/s: 0.11.0.1 > One or more consumers in a consumer-group stop consuming after rebalancing >

[jira] [Updated] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5611: --- Labels: reliability (was: ) > One or more consumers in a consumer-group stop consuming after rebalanc

[jira] [Commented] (KAFKA-3992) InstanceAlreadyExistsException Error for Consumers Starting in Parallel

[ https://issues.apache.org/jira/browse/KAFKA-3992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099963#comment-16099963 ] Charly Molter commented on KAFKA-3992: -- [~ijuma] [~guozhang] thanks for pointing me t

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099943#comment-16099943 ] Ismael Juma commented on KAFKA-5634: [~hachikuji], restarting the follower is not enou

[jira] [Commented] (KAFKA-5621) The producer should retry expired batches when retries are enabled

[ https://issues.apache.org/jira/browse/KAFKA-5621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099910#comment-16099910 ] Ismael Juma commented on KAFKA-5621: [~jjkoshy], [~becket_qin], [~sutambe], what are y

[jira] [Updated] (KAFKA-5498) Connect validation API stops returning recommendations for some fields after the right sequence of requests

[ https://issues.apache.org/jira/browse/KAFKA-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5498: --- Fix Version/s: (was: 1.0.0) > Connect validation API stops returning recommendations for some fiel

[jira] [Updated] (KAFKA-4942) Kafka Connect: Offset committing times out before expected

[ https://issues.apache.org/jira/browse/KAFKA-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4942: --- Fix Version/s: (was: 1.0.0) > Kafka Connect: Offset committing times out before expected > ---

[jira] [Updated] (KAFKA-5450) Scripts to startup Connect in system tests have too short a timeout

[ https://issues.apache.org/jira/browse/KAFKA-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5450: --- Fix Version/s: (was: 1.0.0) > Scripts to startup Connect in system tests have too short a timeout

[jira] [Updated] (KAFKA-5294) PlainSaslServerFactory should allow a null Map in getMechanismNames

[ https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5294: --- Fix Version/s: (was: 1.0.0) > PlainSaslServerFactory should allow a null Map in getMechanismNames

[jira] [Updated] (KAFKA-5164) SetSchemaMetadata does not replace the schemas in structs correctly

[ https://issues.apache.org/jira/browse/KAFKA-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5164: --- Fix Version/s: (was: 1.0.0) > SetSchemaMetadata does not replace the schemas in structs correctly

[jira] [Updated] (KAFKA-5472) Connector validate REST endpoint returning duplicate entries in "groups"

[ https://issues.apache.org/jira/browse/KAFKA-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5472: --- Fix Version/s: (was: 1.0.0) > Connector validate REST endpoint returning duplicate entries in "gro

[jira] [Updated] (KAFKA-5303) FetchRequest doesn't implement toString

[ https://issues.apache.org/jira/browse/KAFKA-5303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5303: --- Fix Version/s: (was: 1.0.0) > FetchRequest doesn't implement toString > --

[jira] [Updated] (KAFKA-4948) Failure in kafka.admin.DescribeConsumerGroupTest.testDescribeExistingGroupWithNoMembersWithNewConsumer

[ https://issues.apache.org/jira/browse/KAFKA-4948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4948: --- Fix Version/s: (was: 1.0.0) > Failure in > kafka.admin.DescribeConsumerGroupTest.testDescribeExis

[jira] [Updated] (KAFKA-5274) Review and improve AdminClient Javadoc for the first release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5274: --- Fix Version/s: (was: 1.0.0) > Review and improve AdminClient Javadoc for the first release (KIP-11

[jira] [Updated] (KAFKA-5147) KafkaProducer's TransactionManager needs a review on synchronization

[ https://issues.apache.org/jira/browse/KAFKA-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5147: --- Fix Version/s: (was: 1.0.0) > KafkaProducer's TransactionManager needs a review on synchronization

[jira] [Updated] (KAFKA-5448) TimestampConverter's "type" config conflicts with the basic Transformation "type" config

[ https://issues.apache.org/jira/browse/KAFKA-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5448: --- Fix Version/s: (was: 1.0.0) > TimestampConverter's "type" config conflicts with the basic Transfor

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5289: --- Fix Version/s: (was: 1.0.0) > One StopReplicaRequest will caused two Responses > -

[jira] [Updated] (KAFKA-5263) kakfa-clients consume 100% CPU with manual partition assignment when network connection is lost

[ https://issues.apache.org/jira/browse/KAFKA-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5263: --- Fix Version/s: (was: 1.0.0) > kakfa-clients consume 100% CPU with manual partition assignment when

[jira] [Updated] (KAFKA-5305) Missing logging information in ReplicaFetcher

[ https://issues.apache.org/jira/browse/KAFKA-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5305: --- Fix Version/s: (was: 1.0.0) > Missing logging information in ReplicaFetcher >

[jira] [Updated] (KAFKA-5486) org.apache.kafka logging should go to server.log

[ https://issues.apache.org/jira/browse/KAFKA-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5486: --- Fix Version/s: (was: 1.0.0) > org.apache.kafka logging should go to server.log > -

[jira] [Updated] (KAFKA-5081) two versions of jackson-annotations-xxx.jar in distribution tgz

[ https://issues.apache.org/jira/browse/KAFKA-5081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5081: --- Fix Version/s: (was: 1.0.0) > two versions of jackson-annotations-xxx.jar in distribution tgz > --

[jira] [Updated] (KAFKA-5229) Reflections logs excessive warnings when scanning classpaths

[ https://issues.apache.org/jira/browse/KAFKA-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5229: --- Fix Version/s: (was: 1.0.0) > Reflections logs excessive warnings when scanning classpaths > -

[jira] [Updated] (KAFKA-5380) Transient test failure: KafkaConsumerTest.testChangingRegexSubscription

[ https://issues.apache.org/jira/browse/KAFKA-5380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5380: --- Fix Version/s: (was: 1.0.0) > Transient test failure: KafkaConsumerTest.testChangingRegexSubscript

[jira] [Updated] (KAFKA-5433) Transient test failure: SaslPlainSslEndToEndAuthorizationTest.testNoProduceWithDescribeAcl

[ https://issues.apache.org/jira/browse/KAFKA-5433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5433: --- Fix Version/s: (was: 1.0.0) > Transient test failure: > SaslPlainSslEndToEndAuthorizationTest.tes

[jira] [Updated] (KAFKA-5475) Connector config validation REST API endpoint not including fields for transformations

[ https://issues.apache.org/jira/browse/KAFKA-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5475: --- Fix Version/s: (was: 1.0.0) > Connector config validation REST API endpoint not including fields f

[jira] [Updated] (KAFKA-4459) rat license check not running in Jenkins

[ https://issues.apache.org/jira/browse/KAFKA-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4459: --- Fix Version/s: (was: 1.0.0) > rat license check not running in Jenkins > -

[jira] [Updated] (KAFKA-5135) Controller Health Metrics (KIP-143)

[ https://issues.apache.org/jira/browse/KAFKA-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5135: --- Fix Version/s: (was: 1.0.0) > Controller Health Metrics (KIP-143) > --

[jira] [Updated] (KAFKA-5051) Avoid DNS reverse lookup in security-critical TLS code path

[ https://issues.apache.org/jira/browse/KAFKA-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5051: --- Fix Version/s: (was: 1.0.0) > Avoid DNS reverse lookup in security-critical TLS code path > --

[jira] [Updated] (KAFKA-5411) Generate javadoc for AdminClient and show configs in documentation

[ https://issues.apache.org/jira/browse/KAFKA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5411: --- Fix Version/s: (was: 1.0.0) > Generate javadoc for AdminClient and show configs in documentation >

[jira] [Created] (KAFKA-5635) KIP-181 Kafka-Connect integrate with kafka ReST Proxy

Dhananjay Patkar created KAFKA-5635: --- Summary: KIP-181 Kafka-Connect integrate with kafka ReST Proxy Key: KAFKA-5635 URL: https://issues.apache.org/jira/browse/KAFKA-5635 Project: Kafka Iss

[jira] [Updated] (KAFKA-5596) TopicCommand methods fail to handle topic name with "."

[ https://issues.apache.org/jira/browse/KAFKA-5596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5596: --- Fix Version/s: (was: 1.1.0) > TopicCommand methods fail to handle topic name with "." > --

[jira] [Updated] (KAFKA-2394) Use RollingFileAppender by default in log4j.properties

[ https://issues.apache.org/jira/browse/KAFKA-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2394: --- Fix Version/s: (was: 1.1.0) 1.0.0 > Use RollingFileAppender by default in log4j

[jira] [Updated] (KAFKA-4423) Drop support for Java 7

[ https://issues.apache.org/jira/browse/KAFKA-4423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4423: --- Fix Version/s: (was: 1.1.0) 1.0.0 > Drop support for Java 7 > -

[jira] [Updated] (KAFKA-5529) ConsoleProducer uses deprecated BaseProducer

[ https://issues.apache.org/jira/browse/KAFKA-5529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5529: --- Fix Version/s: (was: 1.1.0) 2.0.0 > ConsoleProducer uses deprecated BaseProduce

[jira] [Updated] (KAFKA-2651) Remove deprecated config alteration from TopicCommand in 0.9.1.0

[ https://issues.apache.org/jira/browse/KAFKA-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2651: --- Fix Version/s: (was: 1.1.0) 1.0.0 > Remove deprecated config alteration from To

[jira] [Updated] (KAFKA-2983) Remove old Scala clients and all related code, tests, and tools.

[ https://issues.apache.org/jira/browse/KAFKA-2983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2983: --- Fix Version/s: (was: 1.1.0) 2.0.0 > Remove old Scala clients and all related co

[jira] [Updated] (KAFKA-3356) Remove ConsumerOffsetChecker, deprecated in 0.9, in 0.11

[ https://issues.apache.org/jira/browse/KAFKA-3356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3356: --- Fix Version/s: (was: 1.1.0) 1.0.0 > Remove ConsumerOffsetChecker, deprecated in

[jira] [Updated] (KAFKA-2507) Replace ControlledShutdown{Request,Response} with org.apache.kafka.common.requests equivalent

[ https://issues.apache.org/jira/browse/KAFKA-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-2507: --- Fix Version/s: (was: 1.1.0) 2.0.0 > Replace ControlledShutdown{Request,Response

[jira] [Updated] (KAFKA-4935) Consider disabling record level CRC checks for message format V2

[ https://issues.apache.org/jira/browse/KAFKA-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-4935: --- Fix Version/s: (was: 1.0.0) > Consider disabling record level CRC checks for message format V2 > -

[jira] [Commented] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099834#comment-16099834 ] Ismael Juma commented on KAFKA-5634: cc [~lindong] > Replica fetcher thread crashes d

[jira] [Updated] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5634: --- Labels: regression reliability (was: ) > Replica fetcher thread crashes due to OffsetOutOfRangeExcept

[jira] [Updated] (KAFKA-5634) Replica fetcher thread crashes due to OffsetOutOfRangeException

[ https://issues.apache.org/jira/browse/KAFKA-5634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5634: --- Fix Version/s: 0.11.0.1 > Replica fetcher thread crashes due to OffsetOutOfRangeException > --

[jira] [Commented] (KAFKA-5611) One or more consumers in a consumer-group stop consuming after rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099599#comment-16099599 ] Panos Skianis commented on KAFKA-5611: -- Just an observation based on metrics & logs o

[jira] [Comment Edited] (KAFKA-5386) [Kafka Streams] - custom name for state-store change-log topic

[ https://issues.apache.org/jira/browse/KAFKA-5386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099058#comment-16099058 ] Bart Vercammen edited comment on KAFKA-5386 at 7/25/17 7:03 AM: