Can't send json array as configuration

Hi All, When trying to reconfigure kafka standalone connector I am getting below Exception. Could you please help on this? Caused by: com.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of java.lang.String out of START_ARRAY token Error payload: {"connector.class"

Re: [UPDATE] 0.10.1 Release Progress

Well done everyone! Ismael On 4 Oct 2016 5:06 am, "Jason Gustafson" wrote: > Hi Everyone, > > The code freeze is upon us! We've made incredible progress fixing bugs and > improving testing. If your feature or bug fix didn't get in this time, > don't worry since the next release will be here in

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

See Changes: [jason] KAFKA-4248; Consumer should rematch regex immediately in subscribe [jason] MINOR: Follow-up minor improvements/cleanup for KAFKA-3396 -- [...truncated 5785 lines...] kafka

Jenkins build is back to normal : kafka-trunk-jdk8 #944

See

[GitHub] kafka pull request #1956: MINOR: Add upgrade notes for KIP-62

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1956 --- 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 enab

[GitHub] kafka-site pull request #20: new design

Github user derrickdoo commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/20#discussion_r81684259 --- Diff: 0100/protocol.html --- @@ -16,208 +16,215 @@ --> + + + + --- End diff -- Both of these get

Re: [UPDATE] 0.10.1 Release Progress

Thanks for running the release and great to see the progress and focus on shipping a high-quality release. On Mon, Oct 3, 2016 at 9:06 PM Jason Gustafson wrote: > Hi Everyone, > > The code freeze is upon us! We've made incredible progress fixing bugs and > improving testing. If your feature or bu

Re: [UPDATE] 0.10.1 Release Progress

Hi Everyone, The code freeze is upon us! We've made incredible progress fixing bugs and improving testing. If your feature or bug fix didn't get in this time, don't worry since the next release will be here in a few short months. Now the focus is on verifying the release candidates, the first of w

[jira] [Updated] (KAFKA-3175) topic not accessible after deletion even when delete.topic.enable is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3175: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > topic not accessible after de

[jira] [Updated] (KAFKA-3994) Deadlock between consumer heartbeat expiration and offset commit.

[ https://issues.apache.org/jira/browse/KAFKA-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3994: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Deadlock between consumer hea

[GitHub] kafka pull request #1758: KAFKA-4019: Update log cleaner to handle max messa...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1758 --- 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 enab

[jira] [Commented] (KAFKA-4019) LogCleaner should grow read/write buffer to max message size for the topic

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

[jira] [Updated] (KAFKA-4019) LogCleaner should grow read/write buffer to max message size for the topic

[ https://issues.apache.org/jira/browse/KAFKA-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4019: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull requ

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

See Changes: [jason] KAFKA-4248; Consumer should rematch regex immediately in subscribe [jason] MINOR: Follow-up minor improvements/cleanup for KAFKA-3396 -- [...truncated 3811 lines...] kafka.

[GitHub] kafka pull request #1900: [DOCS]: fix ambiguity - consuming by multiple cons...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1900 --- 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 enab

[GitHub] kafka pull request #1956: MINOR: Add upgrade notes for KIP-62

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1956 MINOR: Add upgrade notes for KIP-62 You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka add-kip-62-upgrade-notes Alternatively yo

[GitHub] kafka-site pull request #20: new design

Github user gwenshap commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/20#discussion_r81674590 --- Diff: 0100/protocol.html --- @@ -16,208 +16,215 @@ --> + + --- End diff -- it doesn't look like we are closing th

[GitHub] kafka-site pull request #20: new design

Github user gwenshap commented on a diff in the pull request: https://github.com/apache/kafka-site/pull/20#discussion_r81674610 --- Diff: 0100/protocol.html --- @@ -16,208 +16,215 @@ --> + + + + --- End diff -- couldn't find where

[GitHub] kafka pull request #1955: MINOR: Tweak implementation of `FetchRequest.shuff...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1955 --- 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 enab

[jira] [Updated] (KAFKA-4184) Test failure in ReplicationQuotasTest.shouldBootstrapTwoBrokersWithFollowerThrottle

[ https://issues.apache.org/jira/browse/KAFKA-4184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4184: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Test failure in > Replicatio

[jira] [Updated] (KAFKA-3875) Transient test failure: kafka.api.SslProducerSendTest.testSendNonCompressedMessageWithCreateTime

[ https://issues.apache.org/jira/browse/KAFKA-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3875: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Transient test failure: > ka

[jira] [Updated] (KAFKA-3374) Failure in security rolling upgrade phase 2 system test

[ https://issues.apache.org/jira/browse/KAFKA-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-3374: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Failure in security rolling u

[jira] [Updated] (KAFKA-2363) ProducerSendTest.testCloseWithZeroTimeoutFromCallerThread Transient Failure

[ https://issues.apache.org/jira/browse/KAFKA-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-2363: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > ProducerSendTest.testCloseWit

[jira] [Updated] (KAFKA-4186) Transient failure in KStreamAggregationIntegrationTest.shouldGroupByKey

[ https://issues.apache.org/jira/browse/KAFKA-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4186: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Transient failure in KStreamA

[jira] [Updated] (KAFKA-4222) Transient failure in QueryableStateIntegrationTest.queryOnRebalance

[ https://issues.apache.org/jira/browse/KAFKA-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-4222: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Transient failure in Queryabl

[jira] [Updated] (KAFKA-1377) transient unit test failure in LogOffsetTest

[ https://issues.apache.org/jira/browse/KAFKA-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1377: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > transient unit test failure i

[jira] [Updated] (KAFKA-1573) Transient test failures on LogTest.testCorruptLog

[ https://issues.apache.org/jira/browse/KAFKA-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-1573: --- Fix Version/s: (was: 0.10.1.0) 0.10.1.1 > Transient test failures on Lo

[DISCUSS] Fault injection tests for Kafka

Hi Team Kafka, I was thinking of enhancing our system tests with some fault injections. You know, drop random packets, partition some nodes, delete disks, maybe play with system clocks. Fun stuff :) I was thinking of adding the fault injection to our system tests, so if someone reports a failure

[jira] [Commented] (KAFKA-3491) Issue with consumer close() in finally block with 'enable.auto.commit=true'

[ https://issues.apache.org/jira/browse/KAFKA-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543865#comment-15543865 ] Vahid Hashemian commented on KAFKA-3491: What if by the time we get to the {{catch

[jira] [Commented] (KAFKA-3396) Unauthorized topics are returned to the user

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

[GitHub] kafka pull request #1946: MINOR: Follow-up minor improvements/cleanup for KA...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1946 --- 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 enab

Jenkins build is back to normal : kafka-trunk-jdk7 #1598

See

[jira] [Commented] (KAFKA-3064) Improve resync method to waste less time and data transfer

[ https://issues.apache.org/jira/browse/KAFKA-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543833#comment-15543833 ] Gwen Shapira commented on KAFKA-3064: - I'm wondering if the addition of throttling of

[GitHub] kafka pull request #1955: MINOR: Tweak implementation of `FetchRequest.shuff...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/1955 MINOR: Tweak implementation of `FetchRequest.shuffle` and upgrade.html improvements You can merge this pull request into a Git repository by running: $ git pull https://github.com/ijuma/kafka k

[jira] [Work started] (KAFKA-4211) Change system tests to use the new consumer by default

[ https://issues.apache.org/jira/browse/KAFKA-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-4211 started by Vahid Hashemian. -- > Change system tests to use the new consumer by default > --

[jira] [Commented] (KAFKA-4128) Kafka broker losses messages when zookeeper session times out

[ https://issues.apache.org/jira/browse/KAFKA-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543740#comment-15543740 ] Gwen Shapira commented on KAFKA-4128: - We need more information to understand the caus

[GitHub] kafka pull request #1954: KAFKA-4248: Consumer should rematch regex immediat...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1954 --- 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 enab

[jira] [Commented] (KAFKA-4248) Consumer can return data from old regex subscription in poll()

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

[jira] [Resolved] (KAFKA-4248) Consumer can return data from old regex subscription in poll()

[ https://issues.apache.org/jira/browse/KAFKA-4248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-4248. Resolution: Fixed Issue resolved by pull request 1954 [https://github.com/apache/kafka/pull/

[jira] [Resolved] (KAFKA-1756) never allow the replica fetch size to be less than the max message size

[ https://issues.apache.org/jira/browse/KAFKA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-1756. Resolution: Not A Problem > never allow the replica fetch size to be less than the max message size

[jira] [Commented] (KAFKA-1756) never allow the replica fetch size to be less than the max message size

[ https://issues.apache.org/jira/browse/KAFKA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543715#comment-15543715 ] Ismael Juma commented on KAFKA-1756: This is no longer an issue. As part of KIP-74, if

[jira] [Updated] (KAFKA-1756) never allow the replica fetch size to be less than the max message size

[ https://issues.apache.org/jira/browse/KAFKA-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1756: Priority: Major (was: Blocker) > never allow the replica fetch size to be less than the max message

[jira] [Resolved] (KAFKA-2134) Producer blocked on metric publish

[ https://issues.apache.org/jira/browse/KAFKA-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-2134. - Resolution: Won't Fix Closing due to age > Producer blocked on metric publish > -

[jira] [Resolved] (KAFKA-3466) consumer was stuck , and offset can not be moved

[ https://issues.apache.org/jira/browse/KAFKA-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3466. - Resolution: Not A Bug > consumer was stuck , and offset can not be moved > --

[jira] [Resolved] (KAFKA-3446) SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal

[ https://issues.apache.org/jira/browse/KAFKA-3446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3446. - Resolution: Not A Bug > SIGSEGV (0xb) Crash - libjvm.so / JVM_FindSignal > ---

[jira] [Resolved] (KAFKA-3731) Problems with : Controller 0's connection to broker Node

[ https://issues.apache.org/jira/browse/KAFKA-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3731. - Resolution: Not A Bug > Problems with : Controller 0's connection to broker Node > ---

[jira] [Resolved] (KAFKA-2634) KafkaProducer hangs on future.get()

[ https://issues.apache.org/jira/browse/KAFKA-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-2634. - Resolution: Won't Fix Closing due to lack of activity in ages. > KafkaProducer hangs on future.ge

[jira] [Updated] (KAFKA-1843) Metadata fetch/refresh in new producer should handle all node connection states gracefully

[ https://issues.apache.org/jira/browse/KAFKA-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-1843: Priority: Major (was: Blocker) > Metadata fetch/refresh in new producer should handle all node conn

[jira] [Commented] (KAFKA-3560) Kafka is not working on Solaris

[ https://issues.apache.org/jira/browse/KAFKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543677#comment-15543677 ] Gwen Shapira commented on KAFKA-3560: - Yay :) > Kafka is not working on Solaris > ---

[jira] [Resolved] (KAFKA-3560) Kafka is not working on Solaris

[ https://issues.apache.org/jira/browse/KAFKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira resolved KAFKA-3560. - Resolution: Fixed > Kafka is not working on Solaris > --- > >

[jira] [Commented] (KAFKA-2284) ConsumerRebalanceListener receives wrong type in partitionOwnership values

[ https://issues.apache.org/jira/browse/KAFKA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543673#comment-15543673 ] Gwen Shapira commented on KAFKA-2284: - I'm not sure this is still a blocker since we a

[jira] [Updated] (KAFKA-2284) ConsumerRebalanceListener receives wrong type in partitionOwnership values

[ https://issues.apache.org/jira/browse/KAFKA-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2284: Priority: Major (was: Blocker) > ConsumerRebalanceListener receives wrong type in partitionOwnershi

[jira] [Commented] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[ https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543670#comment-15543670 ] Gwen Shapira commented on KAFKA-2391: - Is this really a blocker? if so, for which rele

[jira] [Updated] (KAFKA-2391) Blocking call such as position(), partitionsFor(), committed() and listTopics() should have a timeout

[ https://issues.apache.org/jira/browse/KAFKA-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2391: Priority: Critical (was: Blocker) > Blocking call such as position(), partitionsFor(), committed()

[GitHub] kafka pull request #1952: MINOR: Only require re-join if the metadata snapsh...

Github user guozhangwang closed the pull request at: https://github.com/apache/kafka/pull/1952 --- 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 i

[GitHub] kafka pull request #1954: KAFKA-4248: Consumer should rematch regex immediat...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/1954 KAFKA-4248: Consumer should rematch regex immediately in subscribe You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka rematch-reg

[jira] [Commented] (KAFKA-4248) Consumer can return data from old regex subscription in poll()

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

[jira] [Created] (KAFKA-4248) Consumer can return data from old regex subscription in poll()

Jason Gustafson created KAFKA-4248: -- Summary: Consumer can return data from old regex subscription in poll() Key: KAFKA-4248 URL: https://issues.apache.org/jira/browse/KAFKA-4248 Project: Kafka

[jira] [Updated] (KAFKA-3910) Cyclic schema support in ConnectSchema and SchemaBuilder

[ https://issues.apache.org/jira/browse/KAFKA-3910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3910: Priority: Major (was: Blocker) > Cyclic schema support in ConnectSchema and SchemaBuilder > ---

[jira] [Commented] (KAFKA-4247) kafka-run-class has potential to add a leading colon to classpath

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

[GitHub] kafka pull request #1953: KAFKA-4247: remove root from traversal path

GitHub user rnpridgeon opened a pull request: https://github.com/apache/kafka/pull/1953 KAFKA-4247: remove root from traversal path You can merge this pull request into a Git repository by running: $ git pull https://github.com/rnpridgeon/kafka KAFKA-4247 Alternatively you ca

[GitHub] kafka pull request #1951: MINOR: Rename property variables to match config

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1951 --- 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 enab

Jenkins build is back to normal : kafka-0.10.1-jdk7 #39

See

[jira] [Commented] (KAFKA-4078) VIP for Kafka doesn't work

[ https://issues.apache.org/jira/browse/KAFKA-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543253#comment-15543253 ] Gwen Shapira commented on KAFKA-4078: - Since it is a VIP, you need to configure advert

[jira] [Updated] (KAFKA-4078) VIP for Kafka doesn't work

[ https://issues.apache.org/jira/browse/KAFKA-4078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4078: Priority: Major (was: Blocker) > VIP for Kafka doesn't work > > >

[jira] [Commented] (KAFKA-4176) Node stopped receiving heartbeat responses once another node started within the same group

[ https://issues.apache.org/jira/browse/KAFKA-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543249#comment-15543249 ] Gwen Shapira commented on KAFKA-4176: - We expect that when we add a new node to a grou

[jira] [Updated] (KAFKA-4176) Node stopped receiving heartbeat responses once another node started within the same group

[ https://issues.apache.org/jira/browse/KAFKA-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-4176: Priority: Major (was: Blocker) > Node stopped receiving heartbeat responses once another node start

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

See Changes: [jason] MINOR: Fix typo in Vagrant README -- [...truncated 3795 lines...] kafka.coordinator.GroupMetadataManagerTest > testExpireGroup STARTED kafka.coordinator.GroupMetadataManag

Re: [DISCUSS] KIP-82 - Add Record Headers

Opposite way around v4 instead of v3 ;) From: Michael Pearce Sent: Monday, October 3, 2016 8:45 PM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-82 - Add Record Headers Thanks guys for spotting this, i have updated KIP-82 to state v3 instead of v4. M

Re: [DISCUSS] KIP-82 - Add Record Headers

Thanks guys for spotting this, i have updated KIP-82 to state v3 instead of v4. Mike. From: Becket Qin Sent: Monday, October 3, 2016 6:18 PM To: dev@kafka.apache.org Subject: Re: [DISCUSS] KIP-82 - Add Record Headers Yes, KIP-74 has already been checked i

Jenkins build is back to normal : kafka-trunk-jdk8 #941

See

[jira] [Created] (KAFKA-4247) kafka-run-class has potential to add a leading colon to classpath

Ryan P created KAFKA-4247: - Summary: kafka-run-class has potential to add a leading colon to classpath Key: KAFKA-4247 URL: https://issues.apache.org/jira/browse/KAFKA-4247 Project: Kafka Issue Type

[jira] [Resolved] (KAFKA-3938) Fix consumer session timeout issue in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3938. -- Resolution: Fixed Fix Version/s: 0.10.1.0 > Fix consumer session timeout issue in Kafka S

[jira] [Updated] (KAFKA-3559) Task creation time taking too long in rebalance callback

[ https://issues.apache.org/jira/browse/KAFKA-3559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3559: - Issue Type: Improvement (was: Sub-task) Parent: (was: KAFKA-3938) > Task creation tim

[jira] [Resolved] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3758. -- Resolution: Fixed > KStream job fails to recover after Kafka broker stopped > --

[jira] [Commented] (KAFKA-3758) KStream job fails to recover after Kafka broker stopped

[ https://issues.apache.org/jira/browse/KAFKA-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542984#comment-15542984 ] Guozhang Wang commented on KAFKA-3758: -- This issue should have been fixed as part of

[jira] [Commented] (KAFKA-3752) Provide a way for KStreams to recover from unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542981#comment-15542981 ] Guozhang Wang commented on KAFKA-3752: -- This issue should have been fixed as part of

[jira] [Resolved] (KAFKA-3752) Provide a way for KStreams to recover from unclean shutdown

[ https://issues.apache.org/jira/browse/KAFKA-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3752. -- Resolution: Fixed > Provide a way for KStreams to recover from unclean shutdown > --

[jira] [Commented] (KAFKA-4246) Discretionary partition assignment on the consumer side not functional

[ https://issues.apache.org/jira/browse/KAFKA-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542950#comment-15542950 ] Vahid Hashemian commented on KAFKA-4246: [~nucatus] Could you share part of your c

Re: [DISCUSS] KIP-82 - Add Record Headers

Yes, KIP-74 has already been checked in. The new FetchRequest/Response version should be V4. :) On Mon, Oct 3, 2016 at 10:14 AM, Sean McCauliff < smccaul...@linkedin.com.invalid> wrote: > Change to public interfaces: > > "Add ProduceRequest/ProduceResponse V3 which uses the new message format. >

Re: [DISCUSS] KIP-82 - Add Record Headers

Change to public interfaces: "Add ProduceRequest/ProduceResponse V3 which uses the new message format. Add FetchRequest/FetchResponse V3 which uses the new message format." When I look at org.apache.kafka.common.requests.FetchResponse on master I see that there is already a version 3. Seems like

[GitHub] kafka pull request #1949: fix a wrong word

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1949 --- 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 enab

[GitHub] kafka pull request #1952: MINOR: Only require re-join if the metadata snapsh...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1952 MINOR: Only require re-join if the metadata snapshot's topics info has changed You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwan

[GitHub] kafka pull request #1900: [DOCS]: fix ambiguity - consuming by multiple cons...

GitHub user pilloPl reopened a pull request: https://github.com/apache/kafka/pull/1900 [DOCS]: fix ambiguity - consuming by multiple consumers, but by exact… In doc it stays: _"Our topic is divided into a set of totally ordered partitions, each of which is consumed by one

[GitHub] kafka pull request #1900: [DOCS]: fix ambiguity - consuming by multiple cons...

Github user pilloPl closed the pull request at: https://github.com/apache/kafka/pull/1900 --- 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 ena

[GitHub] kafka pull request #1951: MINOR: Rename property variables to match config

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/1951 MINOR: Rename property variables to match config ThrottledLeaderReplicationRate* => LeaderReplicationThrottledRate* ThrottledFollowerReplicationRate* => FollowerReplicationThrottledRate* Lea

[GitHub] kafka pull request #1950: MINOR: Add unit tests to the ReassignPartitionsCom...

GitHub user benstopford opened a pull request: https://github.com/apache/kafka/pull/1950 MINOR: Add unit tests to the ReassignPartitionsCommand Adds a bunch of tests to unit tests to the assignment command. Moves the Rack aware test into its own class as it makes use of ZooKee

[GitHub] kafka pull request #1949: fix a wrong word

GitHub user yangwei71 opened a pull request: https://github.com/apache/kafka/pull/1949 fix a wrong word the wrong word in this sentence " allows us to bring machies up in parallel on AWS." . “machies” change to "machines". You can merge this pull request into a Git reposito

[jira] [Updated] (KAFKA-4246) Discretionary partition assignment on the consumer side not functional

[ https://issues.apache.org/jira/browse/KAFKA-4246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandru Ionita updated KAFKA-4246: Description: Trying to manually assign partition/topics to a consumer will not work correct

[jira] [Created] (KAFKA-4246) Discretionary partition assignment on the consumer side not functional

Alexandru Ionita created KAFKA-4246: --- Summary: Discretionary partition assignment on the consumer side not functional Key: KAFKA-4246 URL: https://issues.apache.org/jira/browse/KAFKA-4246 Project: K