[jira] [Commented] (KAFKA-3868) New producer metric record-size-avg does not provide average record size as advertised

[ https://issues.apache.org/jira/browse/KAFKA-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341137#comment-15341137 ] Ewen Cheslack-Postava commented on KAFKA-3868: -- Yeah, ideally we'd be able to report the

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

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

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/922 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Updated] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-3176: - Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341118#comment-15341118 ] ASF GitHub Bot commented on KAFKA-3144: --- Github user vahidhashemian closed the pull request at:

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341119#comment-15341119 ] ASF GitHub Bot commented on KAFKA-3144: --- GitHub user vahidhashemian reopened a pull request:

[GitHub] kafka pull request #1336: KAFKA-3144: Report members with no assigned partit...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1336 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] kafka pull request #1336: KAFKA-3144: Report members with no assigned partit...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341116#comment-15341116 ] ASF GitHub Bot commented on KAFKA-3176: --- GitHub user vahidhashemian reopened a pull request:

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341115#comment-15341115 ] ASF GitHub Bot commented on KAFKA-3176: --- Github user vahidhashemian closed the pull request at:

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only

Re: [VOTE] KIP-55: Secure quotas for authenticated users

Rajini, Another thing that's probably worth thinking through is whether it's better to make the default user quota dynamic as well. So, instead of adding quota.user.producer.default and quota.user.consumer.default in the broker config, another way is to set them using sth like the following.

[jira] [Created] (KAFKA-3883) Remove ThreadedTest from Connect

Ewen Cheslack-Postava created KAFKA-3883: Summary: Remove ThreadedTest from Connect Key: KAFKA-3883 URL: https://issues.apache.org/jira/browse/KAFKA-3883 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341035#comment-15341035 ] ASF GitHub Bot commented on KAFKA-3144: --- GitHub user vahidhashemian reopened a pull request:

[GitHub] kafka pull request #1336: KAFKA-3144: Report members with no assigned partit...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/1336 KAFKA-3144: Report members with no assigned partitions in ConsumerGroupCommand This PR makes a couple of enhancements to the `--describe` option of `ConsumerGroupCommand`: 1. Listing

[GitHub] kafka pull request #1336: KAFKA-3144: Report members with no assigned partit...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/1336 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Commented] (KAFKA-3144) report members with no assigned partitions in ConsumerGroupCommand

[ https://issues.apache.org/jira/browse/KAFKA-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341034#comment-15341034 ] ASF GitHub Bot commented on KAFKA-3144: --- Github user vahidhashemian closed the pull request at:

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341033#comment-15341033 ] ASF GitHub Bot commented on KAFKA-3176: --- GitHub user vahidhashemian reopened a pull request:

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15341032#comment-15341032 ] ASF GitHub Bot commented on KAFKA-3176: --- Github user vahidhashemian closed the pull request at:

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Re: [VOTE] KIP-4 Create Topics Schema

+1 (binding) and thanks for the work on this Grant! -Ewen On Mon, Jun 20, 2016 at 12:18 PM, Gwen Shapira wrote: > +1 (binding) > > On Mon, Jun 20, 2016 at 12:13 PM, Tom Crayford > wrote: > > +1 (non-binding) > > > > On Mon, Jun 20, 2016 at 8:07 PM,

[jira] [Resolved] (KAFKA-3865) Transient failures in org.apache.kafka.connect.runtime.WorkerSourceTaskTest.testSlowTaskStart

[ https://issues.apache.org/jira/browse/KAFKA-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3865. -- Resolution: Fixed Fix Version/s: 0.10.0.1 0.10.1.0 >

[jira] [Commented] (KAFKA-3865) Transient failures in org.apache.kafka.connect.runtime.WorkerSourceTaskTest.testSlowTaskStart

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

[GitHub] kafka pull request #1531: KAFKA-3865: Fix transient failure in WorkerSourceT...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1531 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: [jira] [Commented] (KAFKA-3482) [DOC] - Remove the part about LinkedIn running ZK 3.3.X

Please disregard - transposed digits on entering the pull request. On Mon, Jun 20, 2016 at 10:53 PM, ASF GitHub Bot (JIRA) wrote: > > [ >

[jira] [Resolved] (KAFKA-3869) Fix streams example

[ https://issues.apache.org/jira/browse/KAFKA-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Masahiko Sakamoto resolved KAFKA-3869. -- Resolution: Not A Problem > Fix streams example > --- > >

[jira] [Commented] (KAFKA-3869) Fix streams example

[ https://issues.apache.org/jira/browse/KAFKA-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340956#comment-15340956 ] Masahiko Sakamoto commented on KAFKA-3869: -- Oops. I made this report on v0.10, not on trunk. This

[jira] [Commented] (KAFKA-3482) [DOC] - Remove the part about LinkedIn running ZK 3.3.X

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

[GitHub] kafka pull request #1532: KAFKA-3482: consolidate utility methods to TestUti...

GitHub user bbejeck opened a pull request: https://github.com/apache/kafka/pull/1532 KAFKA-3482: consolidate utility methods to TestUtils, added StreamsTe… …stUtils, added method for pausing tests to TestUtils Changes made: 1. Added utility method for creating

[jira] [Updated] (KAFKA-3842) Add Helper Functions Into TestUtils

[ https://issues.apache.org/jira/browse/KAFKA-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-3842: --- Fix Version/s: (was: 0.10.0.1) 0.10.1.0 Affects Version/s:

[jira] [Comment Edited] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340814#comment-15340814 ] Guozhang Wang edited comment on KAFKA-3705 at 6/21/16 1:09 AM: --- Thanks for

[jira] [Comment Edited] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340814#comment-15340814 ] Guozhang Wang edited comment on KAFKA-3705 at 6/21/16 1:08 AM: --- Thanks for

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340814#comment-15340814 ] Guozhang Wang commented on KAFKA-3705: -- Thanks for the feedbacks! Re 1: Not sure I fully understand

[jira] [Comment Edited] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340779#comment-15340779 ] Jan Filipiak edited comment on KAFKA-3705 at 6/21/16 12:36 AM: --- A few things

[jira] [Commented] (KAFKA-3705) Support non-key joining in KTable

[ https://issues.apache.org/jira/browse/KAFKA-3705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340779#comment-15340779 ] Jan Filipiak commented on KAFKA-3705: - A few things I came accross building the current implementation

[jira] [Commented] (KAFKA-3865) Transient failures in org.apache.kafka.connect.runtime.WorkerSourceTaskTest.testSlowTaskStart

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

[GitHub] kafka pull request #1531: KAFKA-3865: Fix transient failure in WorkerSourceT...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1531 KAFKA-3865: Fix transient failure in WorkerSourceTaskTest.testSlowTaskStart You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka

[jira] [Commented] (KAFKA-3727) Consumer.poll() stuck in loop on non-existent topic manually assigned

[ https://issues.apache.org/jira/browse/KAFKA-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340699#comment-15340699 ] Edoardo Comar commented on KAFKA-3727: -- [~ijuma] and [~hachikuji] referring to your comments in

[GitHub] kafka pull request #1490: KAFKA-3769: Optimize metrics recording overhead

Github user guozhangwang closed the pull request at: https://github.com/apache/kafka/pull/1490 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[jira] [Commented] (KAFKA-3769) KStream job spending 60% of time writing metrics

[ https://issues.apache.org/jira/browse/KAFKA-3769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340675#comment-15340675 ] ASF GitHub Bot commented on KAFKA-3769: --- Github user guozhangwang closed the pull request at:

[jira] [Commented] (KAFKA-3769) KStream job spending 60% of time writing metrics

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

[GitHub] kafka pull request #1530: KAFKA-3769: Create new sensors per-thread in Kafka...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1530 KAFKA-3769: Create new sensors per-thread in KafkaStreams You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

[jira] [Created] (KAFKA-3882) Integration failures on low-end machines

Guozhang Wang created KAFKA-3882: Summary: Integration failures on low-end machines Key: KAFKA-3882 URL: https://issues.apache.org/jira/browse/KAFKA-3882 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3872) OOM while running Kafka Streams integration tests

[ https://issues.apache.org/jira/browse/KAFKA-3872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340668#comment-15340668 ] Guozhang Wang commented on KAFKA-3872: -- I think we should reduce the {{LogCleanerDedupeBufferSize}}

[jira] [Updated] (KAFKA-3874) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion

[ https://issues.apache.org/jira/browse/KAFKA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3874: - Assignee: Damian Guy (was: Guozhang Wang) > Transient test failure: >

[jira] [Commented] (KAFKA-3874) Transient test failure: org.apache.kafka.streams.integration.JoinIntegrationTest.shouldCountClicksPerRegion

[ https://issues.apache.org/jira/browse/KAFKA-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340660#comment-15340660 ] Guozhang Wang commented on KAFKA-3874: -- Seems like other test cases local state store was co-located

Error while sending message to Kafka broker on SSL with Kafka 0.10.0.0

Hi All, I am seeing error while sending message via test producer on SSL port. I am able to successfully send message to non-SSL port. Here is my broker configuration. listeners=SSL://:9093 security.inter.broker.protocol=SSL ssl.client.auth=required ssl.keystore.location=C:/test.jks

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340631#comment-15340631 ] ASF GitHub Bot commented on KAFKA-3176: --- Github user vahidhashemian closed the pull request at:

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340632#comment-15340632 ] ASF GitHub Bot commented on KAFKA-3176: --- GitHub user vahidhashemian reopened a pull request:

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

Build failed in Jenkins: kafka-trunk-jdk8 #711

See Changes: [wangguoz] MINOR: speed up streams integration tests -- [...truncated 6549 lines...] kafka.utils.ReplicationUtilsTest > testUpdateLeaderAndIsr PASSED

Build failed in Jenkins: kafka-trunk-jdk7 #1380

See Changes: [wangguoz] MINOR: speed up streams integration tests -- [...truncated 11385 lines...] org.apache.kafka.streams.processor.internals.PartitionGroupTest > testTimeTracking STARTED

[jira] [Commented] (KAFKA-3868) New producer metric record-size-avg does not provide average record size as advertised

[ https://issues.apache.org/jira/browse/KAFKA-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340565#comment-15340565 ] Jun Rao commented on KAFKA-3868: One caveat is that record() requires synchronization. So, calling it once

[jira] [Commented] (KAFKA-3827) log.message.format.version should default to inter.broker.protocol.version

[ https://issues.apache.org/jira/browse/KAFKA-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340549#comment-15340549 ] Jun Rao commented on KAFKA-3827: [~ewencp], [~ijuma], the issue is that log.message.format.version should

[jira] [Updated] (KAFKA-3849) Avoid polling every second in MirrorMaker if no data is available.

[ https://issues.apache.org/jira/browse/KAFKA-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3849: -- Summary: Avoid polling every second in MirrorMaker if no data is available. (was: Make

[jira] [Assigned] (KAFKA-3868) New producer metric record-size-avg does not provide average record size as advertised

[ https://issues.apache.org/jira/browse/KAFKA-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3868: - Assignee: Liquan Pei > New producer metric record-size-avg does not provide average record size

[jira] [Commented] (KAFKA-3824) Docs indicate auto.commit breaks at least once delivery but that is incorrect

[ https://issues.apache.org/jira/browse/KAFKA-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340464#comment-15340464 ] Jason Gustafson commented on KAFKA-3824: [~beez] Sorry for the confusion. [~liquanpei] already

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340460#comment-15340460 ] ASF GitHub Bot commented on KAFKA-3176: --- Github user vahidhashemian closed the pull request at:

[jira] [Commented] (KAFKA-3176) Allow console consumer to consume from particular partitions when new consumer is used.

[ https://issues.apache.org/jira/browse/KAFKA-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340461#comment-15340461 ] ASF GitHub Bot commented on KAFKA-3176: --- GitHub user vahidhashemian reopened a pull request:

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

Github user vahidhashemian closed the pull request at: https://github.com/apache/kafka/pull/922 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] kafka pull request #922: KAFKA-3176: Add partition/offset options to the new...

GitHub user vahidhashemian reopened a pull request: https://github.com/apache/kafka/pull/922 KAFKA-3176: Add partition/offset options to the new consumer With this pull request the new console consumer can be provided with optional --partition and --offset arguments so only

[GitHub] kafka pull request #1525: MINOR: speed up streams integration tests

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1525 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Created] (KAFKA-3881) Remove the replacing logic from "." to "_" in Fetcher

Guozhang Wang created KAFKA-3881: Summary: Remove the replacing logic from "." to "_" in Fetcher Key: KAFKA-3881 URL: https://issues.apache.org/jira/browse/KAFKA-3881 Project: Kafka Issue

[jira] [Updated] (KAFKA-3880) Disallow Join Windows with size zero

[ https://issues.apache.org/jira/browse/KAFKA-3880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-3880: --- Status: Patch Available (was: Open) https://github.com/apache/kafka/pull/1529 > Disallow

[GitHub] kafka pull request #1529: Kafka-3880: Disallow Join Window with size zero

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/1529 Kafka-3880: Disallow Join Window with size zero You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka kafka-3880-join-windows

[jira] [Assigned] (KAFKA-3829) Warn that kafka-connect group.id must not conflict with connector names

[ https://issues.apache.org/jira/browse/KAFKA-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Liquan Pei reassigned KAFKA-3829: - Assignee: Liquan Pei (was: Ewen Cheslack-Postava) > Warn that kafka-connect group.id must not

Re: [VOTE] KIP-62: Allow consumer to send heartbeats from a background thread

+1 -Jay On Mon, Jun 20, 2016 at 1:39 PM, Jason Gustafson wrote: > Hi All, I've changed the default max.poll.interval.ms in the KIP to 5 > minutes. Unless there are any objections, perhaps we can skip the revote > since this is a small change. In any case, I'll leave the

Build failed in Jenkins: kafka-trunk-jdk7 #1379

See Changes: [me] KAFKA-3864: make field.get return field's default value when needed -- [...truncated 13714 lines...] org.apache.kafka.streams.processor.internals.PartitionGroupTest >

Build failed in Jenkins: kafka-trunk-jdk8 #710

See Changes: [me] KAFKA-3864: make field.get return field's default value when needed -- [...truncated 6560 lines...] kafka.utils.ReplicationUtilsTest > testUpdateLeaderAndIsr STARTED

[jira] [Assigned] (KAFKA-3865) Transient failures in org.apache.kafka.connect.runtime.WorkerSourceTaskTest.testSlowTaskStart

[ https://issues.apache.org/jira/browse/KAFKA-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reassigned KAFKA-3865: -- Assignee: Jason Gustafson > Transient failures in >

Re: [VOTE] KIP-62: Allow consumer to send heartbeats from a background thread

Hi All, I've changed the default max.poll.interval.ms in the KIP to 5 minutes. Unless there are any objections, perhaps we can skip the revote since this is a small change. In any case, I'll leave the vote open for another day. Thanks, Jason On Mon, Jun 20, 2016 at 12:39 PM, Ismael Juma

[jira] [Commented] (KAFKA-3879) KafkaConsumer with auto commit enabled gets stuck when killed after broker is dead

[ https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15340283#comment-15340283 ] Ashish K Singh commented on KAFKA-3879: --- [~hachikuji] did you guys ever hit this? I am thinking of

Re: [VOTE] KIP-62: Allow consumer to send heartbeats from a background thread

On Mon, Jun 20, 2016 at 9:32 PM, Jay Kreps wrote: > Also, checked exceptions? Really Ewen??? :-) > Haha, yeah. I thought checked exceptions were universally disliked. People who favour static typing tend to prefer Disjunction/Either and the rest tend to prefer unchecked

[jira] [Created] (KAFKA-3880) Disallow Join Windows with size zero

Matthias J. Sax created KAFKA-3880: -- Summary: Disallow Join Windows with size zero Key: KAFKA-3880 URL: https://issues.apache.org/jira/browse/KAFKA-3880 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-3864) Kafka Connect Struct.get returning defaultValue from Struct not the field schema

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

[jira] [Resolved] (KAFKA-3864) Kafka Connect Struct.get returning defaultValue from Struct not the field schema

[ https://issues.apache.org/jira/browse/KAFKA-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3864. -- Resolution: Fixed Issue resolved by pull request 1528

[GitHub] kafka pull request #1528: KAFKA-3864: make field.get return field's default ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1528 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Re: [VOTE] KIP-62: Allow consumer to send heartbeats from a background thread

Jason, yeah I think raising to 3 minutes (or better yet 5 mins) would be better since fewer people would hit it. I do think guessing is going to be kind of annoying here since you will eventually hit the limit in prod and curse us since it wasn't a limit you intended to set, but at least setting a

[jira] [Created] (KAFKA-3879) KafkaConsumer with auto commit enabled gets stuck when killed after broker is dead

Ashish K Singh created KAFKA-3879: - Summary: KafkaConsumer with auto commit enabled gets stuck when killed after broker is dead Key: KAFKA-3879 URL: https://issues.apache.org/jira/browse/KAFKA-3879

Re: [VOTE] KIP-4 Create Topics Schema

+1 (binding) On Mon, Jun 20, 2016 at 12:13 PM, Tom Crayford wrote: > +1 (non-binding) > > On Mon, Jun 20, 2016 at 8:07 PM, Harsha wrote: > >> +1 (binding) >> -Harsha >> >> On Mon, Jun 20, 2016, at 11:33 AM, Ismael Juma wrote: >> > +1 (binding) >> > >> > On

Re: [VOTE] KIP-4 Create Topics Schema

+1 (non-binding) On Mon, Jun 20, 2016 at 8:07 PM, Harsha wrote: > +1 (binding) > -Harsha > > On Mon, Jun 20, 2016, at 11:33 AM, Ismael Juma wrote: > > +1 (binding) > > > > On Mon, Jun 20, 2016 at 8:27 PM, Dana Powers > > wrote: > > > > > +1 -- thanks for

[jira] [Updated] (KAFKA-3879) KafkaConsumer with auto commit enabled gets stuck when killed after broker is dead

[ https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3879: -- Affects Version/s: 0.10.0.0 > KafkaConsumer with auto commit enabled gets stuck when killed

[jira] [Updated] (KAFKA-3879) KafkaConsumer with auto commit enabled gets stuck when killed after broker is dead

[ https://issues.apache.org/jira/browse/KAFKA-3879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish K Singh updated KAFKA-3879: -- Fix Version/s: 0.10.0.1 > KafkaConsumer with auto commit enabled gets stuck when killed after

[DISCUSS] KIP-4 Delete Topic Schema

The KIP-4 Create Topic Schema vote is close to passing so I would like to start the discussion for the DeleteTopic request/response and server side implementation. Details for this implementation can be read here:

Re: [VOTE] KIP-4 Create Topics Schema

+1 (binding) -Harsha On Mon, Jun 20, 2016, at 11:33 AM, Ismael Juma wrote: > +1 (binding) > > On Mon, Jun 20, 2016 at 8:27 PM, Dana Powers > wrote: > > > +1 -- thanks for the update > > > > On Mon, Jun 20, 2016 at 10:49 AM, Grant Henke wrote: > > >

Re: [VOTE] KIP-62: Allow consumer to send heartbeats from a background thread

Hey Jay, Thanks for the comments. I'd be sorely tempted to default to an infinite value for max.poll.interval.ms if we offered a separate rebalance timeout, but it seems a little dangerous as long as we use the same setting for both. In the worst case, a live-locked process could indefinitely

Re: [VOTE] KIP-4 Create Topics Schema

+1 (binding) On Mon, Jun 20, 2016 at 8:27 PM, Dana Powers wrote: > +1 -- thanks for the update > > On Mon, Jun 20, 2016 at 10:49 AM, Grant Henke wrote: > > I have update the patch and wiki based on the feedback in the discussion > > thread. The only

Re: [VOTE] KIP-4 Create Topics Schema

+1 -- thanks for the update On Mon, Jun 20, 2016 at 10:49 AM, Grant Henke wrote: > I have update the patch and wiki based on the feedback in the discussion > thread. The only change is that instead of logging and disconnecting in the > case of invalid messages (duplicate

Re: [VOTE] KIP-4 Create Topics Schema

I have update the patch and wiki based on the feedback in the discussion thread. The only change is that instead of logging and disconnecting in the case of invalid messages (duplicate topics or both arguments) we now return and InvalidRequest error back to the client for that topic. I would like

[jira] [Commented] (KAFKA-3878) Support exponential backoff for broker reconnect attempts

[ https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339941#comment-15339941 ] Dana Powers commented on KAFKA-3878: Proposed implementation at

Re: Operator order

You can do a conditional branching by using KStream.branch(Predicate...). You can then merge multiple streams using KStreamBuilder.merge(KStream...). -Yasuhiro On Mon, Jun 20, 2016 at 4:45 AM, Jeyhun Karimov wrote: > Hi Guozhang, > > Thank you for your reply. Yes, it is

[jira] [Commented] (KAFKA-3864) Kafka Connect Struct.get returning defaultValue from Struct not the field schema

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

[GitHub] kafka pull request #1528: KAFKA-3864: make field.get return field's default ...

GitHub user rollulus opened a pull request: https://github.com/apache/kafka/pull/1528 KAFKA-3864: make field.get return field's default value when needed And not the containing struct's default value. The contribution is my original work and that I license the work to the

[jira] [Created] (KAFKA-3878) Support exponential backoff for broker reconnect attempts

Dana Powers created KAFKA-3878: -- Summary: Support exponential backoff for broker reconnect attempts Key: KAFKA-3878 URL: https://issues.apache.org/jira/browse/KAFKA-3878 Project: Kafka Issue

[jira] [Commented] (KAFKA-3809) Auto-generate documentation for topic-level configuration

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

[GitHub] kafka pull request #1527: KAFKA-3809: Auto-generate documentation for topic-...

GitHub user wushujames opened a pull request: https://github.com/apache/kafka/pull/1527 KAFKA-3809: Auto-generate documentation for topic-level configuration @ijuma said that it would make sense to split out this work from KAFKA-3234, since KAFKA-3234 had both a mechanical change

[jira] [Commented] (KAFKA-3837) Report the name of the blocking thread when throwing ConcurrentModificationException

[ https://issues.apache.org/jira/browse/KAFKA-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15339884#comment-15339884 ] ASF GitHub Bot commented on KAFKA-3837: --- Github user bharatviswa504 closed the pull request at:

  1   2   >