[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

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

[GitHub] kafka pull request #862: KAFKA-3199: LoginManager should allow using an exis...

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

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

See

[jira] [Commented] (KAFKA-3450) Producer blocks on send to topic that doesn't exist if auto create is disabled

[ https://issues.apache.org/jira/browse/KAFKA-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043829#comment-16043829 ] Soumya Bhaumik commented on KAFKA-3450: --- Just checking to see if there is any update on this. I am

[jira] [Reopened] (KAFKA-5327) Console Consumer should only poll for up to max messages

[ https://issues.apache.org/jira/browse/KAFKA-5327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson reopened KAFKA-5327: I have reverted this change in KAFKA-5414 since it breaks existing usage. It seems like a

[jira] [Commented] (KAFKA-5414) Console consumer offset commit regression

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

[GitHub] kafka pull request #3277: KAFKA-5414: Revert "KAFKA-5327: ConsoleConsumer sh...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3277 --- 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] [Resolved] (KAFKA-5414) Console consumer offset commit regression

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

[jira] [Assigned] (KAFKA-5152) Kafka Streams keeps restoring state after shutdown is initiated during startup

[ https://issues.apache.org/jira/browse/KAFKA-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5152: -- Assignee: Matthias J. Sax > Kafka Streams keeps restoring state after shutdown is

[jira] [Updated] (KAFKA-5152) Kafka Streams keeps restoring state after shutdown is initiated during startup

[ https://issues.apache.org/jira/browse/KAFKA-5152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5152: --- Fix Version/s: 0.11.0.1 0.10.2.2 > Kafka Streams keeps restoring state

[jira] [Commented] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043758#comment-16043758 ] Apurva Mehta commented on KAFKA-5415: - The interesting thing is that it reproduces consistently on

[jira] [Commented] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043753#comment-16043753 ] Matthias J. Sax commented on KAFKA-5242: While trying to add a new integration test for Streams

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043741#comment-16043741 ] Apurva Mehta edited comment on KAFKA-5415 at 6/9/17 12:59 AM: -- Incriminating

[jira] [Updated] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-5242: --- Fix Version/s: 0.11.0.1 0.10.2.2 > add max_number _of_retries to

[jira] [Assigned] (KAFKA-5242) add max_number _of_retries to exponential backoff strategy

[ https://issues.apache.org/jira/browse/KAFKA-5242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reassigned KAFKA-5242: -- Assignee: Matthias J. Sax > add max_number _of_retries to exponential backoff strategy

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommit state

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Summary: TransactionCoordinator gets stuck in PrepareCommit state (was: TransactionCoordinator

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043741#comment-16043741 ] Apurva Mehta edited comment on KAFKA-5415 at 6/9/17 12:50 AM: -- Incriminating

[jira] [Comment Edited] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043741#comment-16043741 ] Apurva Mehta edited comment on KAFKA-5415 at 6/9/17 12:51 AM: -- Incriminating

[jira] [Commented] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043741#comment-16043741 ] Apurva Mehta commented on KAFKA-5415: - Incriminating evidence from the logs. 1. Tail of the

[jira] [Commented] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043731#comment-16043731 ] Apurva Mehta commented on KAFKA-5415: - Logs from one such incident:

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Attachment: 6.tgz > TransactionCoordinator gets stuck in PrepareCommits state. >

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Labels: exactly-once (was: ) > TransactionCoordinator gets stuck in PrepareCommits state. >

[jira] [Updated] (KAFKA-5415) TransactionCoordinator gets stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Summary: TransactionCoordinator gets stuck in PrepareCommits state. (was: TransactionCoordinator

[jira] [Updated] (KAFKA-5415) TransactionCoordinator get stuck in PrepareCommits state.

[ https://issues.apache.org/jira/browse/KAFKA-5415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5415: Summary: TransactionCoordinator get stuck in PrepareCommits state. (was: TransactionCoordinator )

[jira] [Created] (KAFKA-5415) TransactionCoordinator

Apurva Mehta created KAFKA-5415: --- Summary: TransactionCoordinator Key: KAFKA-5415 URL: https://issues.apache.org/jira/browse/KAFKA-5415 Project: Kafka Issue Type: Bug Reporter:

[GitHub] kafka pull request #3278: WIP: MINOR: Add logging and a small bug fix for th...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3278 WIP: MINOR: Add logging and a small bug fix for the transaction coordinator You can merge this pull request into a Git repository by running: $ git pull https://github.com/apurvam/kafka

[jira] [Commented] (KAFKA-5414) Console consumer offset commit regression

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

[GitHub] kafka pull request #3277: KAFKA-5414: Revert "KAFKA-5327: ConsoleConsumer sh...

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka/pull/3277 KAFKA-5414: Revert "KAFKA-5327: ConsoleConsumer should manually commi… …t offsets for records that are returned in receive()" This reverts commit

Jenkins build is back to normal : kafka-0.11.0-jdk7 #126

See

[jira] [Created] (KAFKA-5414) Console consumer offset commit regression

Jason Gustafson created KAFKA-5414: -- Summary: Console consumer offset commit regression Key: KAFKA-5414 URL: https://issues.apache.org/jira/browse/KAFKA-5414 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5361) Add EOS integration tests for Streams API

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

Re: Pull-Requests not worked on

Hi all, A few clarifications: 1. Anyone can see the console output for a failed job, a login is not required for that. 2. One of the reasons why some PRs remain open even if they should be closed is that we have no way to close PRs ourselves without referencing them in a commit or asking Apache

[GitHub] kafka pull request #3276: KAFKA-5361: Add more integration tests for Streams...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3276 KAFKA-5361: Add more integration tests for Streams EOS - multi-subtopology tests - fencing test You can merge this pull request into a Git repository by running: $ git pull

Re: Pull-Requests not worked on

I always thought that we had to repush a commit or close/open the PR in order to retrigger the build. This is the first time I've heard that you can do that. Does "retest this please" cause the tests to be re-run, simply because it's a comment on a PR? Or is it some magic with how we set

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

See Changes: [cshapi] KAFKA-5411: AdminClient javadoc and documentation improvements [wangguoz] MINOR: disable flaky Streams EOS integration tests -- [...truncated

[jira] [Created] (KAFKA-5413) Log cleaner fails due to large offset in segment file

Nicholas Ngorok created KAFKA-5413: -- Summary: Log cleaner fails due to large offset in segment file Key: KAFKA-5413 URL: https://issues.apache.org/jira/browse/KAFKA-5413 Project: Kafka

[GitHub] kafka pull request #3275: HOTFIX: use atomic boolean for inject errors in st...

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/3275 HOTFIX: use atomic boolean for inject errors in streams eos integration test Originally we assume the task will be created exactly three times (twice upon starting up, once for each thread,

[jira] [Resolved] (KAFKA-5382) Log recovery can fail if topic names contain one of the index suffixes

[ https://issues.apache.org/jira/browse/KAFKA-5382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-5382. Resolution: Fixed Fix Version/s: (was: 0.10.2.2) 0.11.0.0.

[jira] [Updated] (KAFKA-2378) Add Connect embedded API

[ https://issues.apache.org/jira/browse/KAFKA-2378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-2378: Summary: Add Connect embedded API (was: Add Copycat embedded API) > Add Connect embedded API >

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

See

Build failed in Jenkins: kafka-0.11.0-jdk7 #125

See Changes: [wangguoz] KAFKA-5362: Add EOS system tests for Streams API -- [...truncated 2.37 MB...] org.apache.kafka.streams.integration.QueryableStateIntegrationTest >

[jira] [Commented] (KAFKA-5317) Update KIP-98 to reflect changes during implementation.

[ https://issues.apache.org/jira/browse/KAFKA-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043562#comment-16043562 ] Ismael Juma commented on KAFKA-5317: Technically, it should be. > Update KIP-98 to reflect changes

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

See

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

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

[GitHub] kafka pull request #3274: KAFKA-3199 LoginManager should allow using an exis...

GitHub user utenakr opened a pull request: https://github.com/apache/kafka/pull/3274 KAFKA-3199 LoginManager should allow using an existing Subject LoginManager or KerberosLogin (for > kafka 0.10) should allow using an existing Subject. If there's an existing subject, the Jaas

[GitHub] kafka pull request #3272: MINOR: disable flaky Streams EOS integration tests

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3272 --- 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] [Commented] (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:comment-tabpanel=16043546#comment-16043546 ] ASF GitHub Bot commented on KAFKA-5411: --- Github user asfgit closed the pull request at:

[GitHub] kafka pull request #3271: KAFKA-5411: AdminClient javadoc and documentation ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3271 --- 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-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 ] Gwen Shapira updated KAFKA-5411: Resolution: Fixed Fix Version/s: 0.11.1.0 Status: Resolved (was: Patch Available)

[GitHub] kafka pull request #3272: MINOR: disable flaky Streams EOS integration tests

GitHub user mjsax reopened a pull request: https://github.com/apache/kafka/pull/3272 MINOR: disable flaky Streams EOS integration tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka minor-disable-eos-tests

Info regarding kafka topic

Hi, I have a 3 node Kafka Broker cluster. I have created a topic and the leader for the topic is broker 1(1001). And the broker got died. But when I see the information in zookeeper for the topic, I see the leader is still set to broker 1 (1001) and isr is set to 1001. Is this a bug in kafka, as

[jira] [Commented] (KAFKA-5317) Update KIP-98 to reflect changes during implementation.

[ https://issues.apache.org/jira/browse/KAFKA-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043541#comment-16043541 ] Gwen Shapira commented on KAFKA-5317: - I understand the importance, but is it really a release

[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=16043528#comment-16043528 ] Guozhang Wang commented on KAFKA-4628: -- [~dminkovsky] Thanks for sharing your use cases. We are

Re: [VOTE] KIP-134: Delay initial consumer group rebalance

Just recapping on client-side v.s. broker-side config: we did discuss about adding this as a client-side config and bump up join-group request (I think both Ismael and Ewen questioned about it) to include this configured value to the broker. I cannot remember if there is any strong motivations

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043503#comment-16043503 ] Adam Kunicki commented on KAFKA-3199: - Yes, thank you! [~jisunkim] > LoginManager should allow using

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Note that although the internal `AbstractStoreSupplier` does maintain the key-value serdes, we do not enforce the interface of `StateStoreSupplier` to always retain that information, and hence we cannot assume that StateStoreSuppliers always retain key / value serdes. On Thu, Jun 8, 2017 at 11:51

[jira] [Comment Edited] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043494#comment-16043494 ] Jay Kreps edited comment on KAFKA-1955 at 6/8/17 9:43 PM: -- I think the patch I

[jira] [Comment Edited] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043494#comment-16043494 ] Jay Kreps edited comment on KAFKA-1955 at 6/8/17 9:41 PM: -- I think the patch I

[jira] [Commented] (KAFKA-1955) Explore disk-based buffering in new Kafka Producer

[ https://issues.apache.org/jira/browse/KAFKA-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043494#comment-16043494 ] Jay Kreps commented on KAFKA-1955: -- I think the patch I submitted was kind of a cool hack, but after

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

I chose the current way so if you make multiple tables you don't need to supply the serde and initializer multiple times. It is true that you wouldnt need the serde if you use a statestoresupplier but I think we could note that in the method call. I am fine with the first option if thats what

Re: Kafka-2170 & Kafka-1194

I think this is an area that needs some more work. I don't think we'll have a fix for it in 0.11. best, Colin On Thu, Jun 1, 2017, at 05:51, Jacob Braaten wrote: > Hello, > > I am emailing to check on the status of the two bugs above. Both pertain > to > the same issue of not being able to

[jira] [Commented] (KAFKA-3199) LoginManager should allow using an existing Subject

[ https://issues.apache.org/jira/browse/KAFKA-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043484#comment-16043484 ] Ji sun commented on KAFKA-3199: --- Hi Adam, do you mind me taking this jira for Kafka 0.10? > LoginManager

[jira] [Commented] (KAFKA-5402) JmxReporter Fetch metrics for kafka.server should not be created when client quotas are not enabled

[ https://issues.apache.org/jira/browse/KAFKA-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043480#comment-16043480 ] Jun Rao commented on KAFKA-5402: Not sure if this is the same as KAFKA-3980. Currently, if a metric is not

[jira] [Updated] (KAFKA-5336) ListGroup requires Describe on Cluster, but the command-line AclCommand tool does not allow this to be set

[ https://issues.apache.org/jira/browse/KAFKA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-5336: --- Summary: ListGroup requires Describe on Cluster, but the command-line AclCommand tool does

[GitHub] kafka-site issue #60: Update delivery semantics section for KIP-98

Github user hachikuji commented on the issue: https://github.com/apache/kafka-site/pull/60 cc @guozhangwang @apurva @ijuma --- 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

[jira] [Resolved] (KAFKA-5336) The required ACL permission for ListGroup is invalid

[ https://issues.apache.org/jira/browse/KAFKA-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe resolved KAFKA-5336. Resolution: Duplicate Fix Version/s: 0.11.0.0 KAFKA-5292 in 0.11 added {{Describe}}

[GitHub] kafka-site pull request #60: Update delivery semantics section for KIP-98

GitHub user hachikuji opened a pull request: https://github.com/apache/kafka-site/pull/60 Update delivery semantics section for KIP-98 You can merge this pull request into a Git repository by running: $ git pull https://github.com/hachikuji/kafka-site

[jira] [Commented] (KAFKA-3925) Default log.dir=/tmp/kafka-logs is unsafe

[ https://issues.apache.org/jira/browse/KAFKA-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043472#comment-16043472 ] Ismael Juma commented on KAFKA-3925: Unit tests set the log.dir explicitly so they would not be

[jira] [Commented] (KAFKA-3925) Default log.dir=/tmp/kafka-logs is unsafe

[ https://issues.apache.org/jira/browse/KAFKA-3925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043469#comment-16043469 ] Colin P. McCabe commented on KAFKA-3925: The issue with {{/var}} is that if you run Kafka as an

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

See Changes: [jason] HOTFIX: for flaky Streams EOS integration tests -- [...truncated 2.40 MB...] org.apache.kafka.streams.kstream.internals.KStreamKStreamLeftJoinTest >

[jira] [Commented] (KAFKA-5362) Add EOS system tests for Streams API

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

[jira] [Resolved] (KAFKA-5362) Add EOS system tests for Streams API

[ https://issues.apache.org/jira/browse/KAFKA-5362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5362. -- Resolution: Fixed Issue resolved by pull request 3201

[GitHub] kafka pull request #3201: KAFKA-5362: Add EOS system tests for Streams API

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

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

See Changes: [wangguoz] KAFKA-5357 follow-up: Yammer metrics, not Kafka Metrics -- [...truncated 4.58 MB...]

Re: Pull-Requests not worked on

So, there has been some instability in the junit tests recently due to some big features landing. This is starting to improve a lot, though, so hopefully it won't be a problem for much longer. If you do hit what you think is a bogus unit test failure, you can type "retest this please" in the PR

[jira] [Issue Comment Deleted] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viktor Somogyi updated KAFKA-1044: -- Comment: was deleted (was: @ewencp, thank you for your help. I've started this task and all in

[GitHub] kafka pull request #3272: MINOR: disable flaky Streams EOS integration tests

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

[GitHub] kafka pull request #3273: HOTFIX: for flaky Streams EOS integration tests

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

Build failed in Jenkins: kafka-0.11.0-jdk7 #123

See Changes: [wangguoz] KAFKA-5357 follow-up: Yammer metrics, not Kafka Metrics -- [...truncated 2.38 MB...]

[jira] [Commented] (KAFKA-1044) change log4j to slf4j

[ https://issues.apache.org/jira/browse/KAFKA-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043329#comment-16043329 ] Viktor Somogyi commented on KAFKA-1044: --- @ewencp, thank you for your help. I've started this task

[jira] [Commented] (KAFKA-5409) Providing a custom client-id to the ConsoleProducer tool

[ https://issues.apache.org/jira/browse/KAFKA-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043268#comment-16043268 ] Bharat Viswanadham commented on KAFKA-5409: --- Hi Paolo, Ya missed that point. Ya I think to use

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

See

[jira] [Commented] (KAFKA-5357) StackOverFlow error in transaction coordinator

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

[GitHub] kafka pull request #3242: KAFKA-5357 follow-up: Yammer metrics, not Kafka Me...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3242 --- 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: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

Another reason for the serde not to be in the first cogroup call, is that the serde should not be required if you pass a StateStoreSupplier to aggregate() Regarding the aggregated type I don't the why initializer should be favored over aggregator to define the type. In my mind separating the

Re: [DISCUSS] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

Hey Ismael, Thanks for the feedback! Could you please vote for the KIP if it looks good? Then I will find two more committers to vote as well. Thanks, Dong On Tue, May 30, 2017 at 9:08 AM, Dong Lin wrote: > Thanks Edoardo and everyone for the comment! That is a very good

Re: [VOTE] KIP-164 Add unavailablePartitionCount and per-partition Unavailable metrics

Thanks to everyone who voted! I am waiting for committers to vote before closing this thread. On Mon, Jun 5, 2017 at 6:10 AM, Bill Bejeck wrote: > Thanks for the KIP. > > +1 > > -Bill > > On Mon, Jun 5, 2017 at 8:51 AM, Edoardo Comar wrote: > > > +1 (non

[DISCUSS] KIP-163: Lower the Minimum Required ACL Permission of OffsetFetch

Hi all, I'm resending my earlier note hoping it would spark some conversation this time around :) Thanks. --Vahid From: "Vahid S Hashemian" To: dev , "Kafka User" Date: 05/30/2017 08:33 AM Subject:

[jira] [Comment Edited] (KAFKA-5409) Providing a custom client-id to the ConsoleProducer tool

[ https://issues.apache.org/jira/browse/KAFKA-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043185#comment-16043185 ] Paolo Patierno edited comment on KAFKA-5409 at 6/8/17 6:23 PM: --- Hi Bharat,

[jira] [Commented] (KAFKA-5409) Providing a custom client-id to the ConsoleProducer tool

[ https://issues.apache.org/jira/browse/KAFKA-5409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043185#comment-16043185 ] Paolo Patierno commented on KAFKA-5409: --- Hi Bharat, you are right but ... inside the

Re: [Vote] KIP-150 - Kafka-Streams Cogroup

I think we can continue on this voting thread. Currently we have one binding vote and 2 non-binging votes. I would like to call out for other people especially committers to also take a look at this proposal and vote. Guozhang On Wed, Jun 7, 2017 at 6:37 PM, Kyle Winkelman

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

On a second thought... This is the current proposal API ``` CogroupedKStream cogroup(final Initializer initializer, final Aggregator aggregator, final Serde aggValueSerde) ``` If we do not have the initializer in the first co-group it might be a bit awkward for users to specify the

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

This suggestion lgtm. I would vote for the first alternative than adding it to the `KStreamBuilder` though. On Thu, Jun 8, 2017 at 10:58 AM, Xavier Léauté wrote: > I have a minor suggestion to make the API a little bit more symmetric. > I feel it would make more sense to

Re: [DISCUSS] KIP-150 - Kafka-Streams Cogroup

I have a minor suggestion to make the API a little bit more symmetric. I feel it would make more sense to move the initializer and serde to the final aggregate statement, since the serde only applies to the state store, and the initializer doesn't bear any relation to the first group in

[GitHub] kafka pull request #3273: HOTFIX: for flaky Streams EOS integration tests

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3273 HOTFIX: for flaky Streams EOS integration tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka hotfix-flaky-stream-eos-test

Re: [DISCUSS] KIP-167: Add a restoreAll method to StateRestoreCallback

Guozhang, Damian thanks for the comments. Giving developers the ability to hook into StateStore recovery phases was part of my original intent. However the state the KIP is in now won't provide this functionality. As a result I'll be doing a significant revision of KIP-167. I'll be sure to

[GitHub] kafka pull request #3272: MINOR: disable flaky Streams EOS integration tests

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3272 MINOR: disable flaky Streams EOS integration tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka minor-disable-eos-tests

[jira] [Commented] (KAFKA-5412) Using connect-console-sink/source.properties raises an exception related to "file" property not found

[ https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043034#comment-16043034 ] Paolo Patierno commented on KAFKA-5412: --- Yes I agree this is a better solution. I'd like to work on

[jira] [Updated] (KAFKA-5412) Using connect-console-sink/source.properties raises an exception related to "file" property not found

[ https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5412: - Affects Version/s: (was: 0.11.1.0) 0.11.0.0 > Using

[jira] [Commented] (KAFKA-5412) Using connect-console-sink/source.properties raises an exception related to "file" property not found

[ https://issues.apache.org/jira/browse/KAFKA-5412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16043018#comment-16043018 ] Randall Hauch commented on KAFKA-5412: -- I believe the proper correction would be to add a null

  1   2   >