[jira] [Commented] (KAFKA-4400) Prefix for sink task consumer groups should be configurable

[ https://issues.apache.org/jira/browse/KAFKA-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042325#comment-16042325 ] Paolo Patierno commented on KAFKA-4400: --- [~ewencp] I don't see activity on this sinc

[jira] [Commented] (KAFKA-5153) KAFKA Cluster : 0.10.2.0 : Servers Getting disconnected : Service Impacting

[ https://issues.apache.org/jira/browse/KAFKA-5153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042350#comment-16042350 ] Qingsong Xie commented on KAFKA-5153: - [~dhirajpraj] hi, this bug has been fixed in 0.

[jira] [Commented] (KAFKA-4633) Always use regex pattern subscription to avoid auto create topics

[ https://issues.apache.org/jira/browse/KAFKA-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042360#comment-16042360 ] Andres Gomez Ferrer commented on KAFKA-4633: [~mjsax] ok!! I understand, so I

[jira] [Created] (KAFKA-5408) Using the ConsumerRecord instead of BaseConsumerRecord in the ConsoleConsumer

Paolo Patierno created KAFKA-5408: - Summary: Using the ConsumerRecord instead of BaseConsumerRecord in the ConsoleConsumer Key: KAFKA-5408 URL: https://issues.apache.org/jira/browse/KAFKA-5408 Project

[jira] [Updated] (KAFKA-5408) Using the ConsumerRecord instead of BaseConsumerRecord in the ConsoleConsumer

[ https://issues.apache.org/jira/browse/KAFKA-5408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paolo Patierno updated KAFKA-5408: -- Description: Hi, because the BaseConsumerRecord is marked as deprecated and will be removed in

[GitHub] kafka pull request #3267: MINOR: more details in error message descriptions

GitHub user reftel opened a pull request: https://github.com/apache/kafka/pull/3267 MINOR: more details in error message descriptions You can merge this pull request into a Git repository by running: $ git pull https://github.com/reftel/kafka feature/error_descriptions Altern

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

Paolo Patierno created KAFKA-5409: - Summary: Providing a custom client-id to the ConsoleProducer tool Key: KAFKA-5409 URL: https://issues.apache.org/jira/browse/KAFKA-5409 Project: Kafka Issu

[jira] [Commented] (KAFKA-4501) Support Java 9

[ https://issues.apache.org/jira/browse/KAFKA-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042438#comment-16042438 ] Ismael Juma commented on KAFKA-4501: I had a quick look at making the build work with

[jira] [Updated] (KAFKA-5257) Change Default unclean.leader.election.enabled from True to False

[ https://issues.apache.org/jira/browse/KAFKA-5257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5257: --- Summary: Change Default unclean.leader.election.enabled from True to False (was: CLONE - Change Defau

[jira] [Created] (KAFKA-5410) Fix taskClass() method name in Connector and flush() signature in SinkTask

Paolo Patierno created KAFKA-5410: - Summary: Fix taskClass() method name in Connector and flush() signature in SinkTask Key: KAFKA-5410 URL: https://issues.apache.org/jira/browse/KAFKA-5410 Project: K

[jira] [Commented] (KAFKA-5410) Fix taskClass() method name in Connector and flush() signature in SinkTask

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

[GitHub] kafka pull request #3268: KAFKA-5410: Fix taskClass() method name in Connect...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/3268 KAFKA-5410: Fix taskClass() method name in Connector and flush() signature in SinkTask You can merge this pull request into a Git repository by running: $ git pull https://github.com/ppati

[jira] [Commented] (KAFKA-2729) Cached zkVersion not equal to that in zookeeper, broker not recovering.

[ https://issues.apache.org/jira/browse/KAFKA-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042543#comment-16042543 ] Pablo commented on KAFKA-2729: -- Guys, this issue is not only affecting to 0.8.2.1 as many peo

[GitHub] kafka pull request #3256: MINOR: Updated .gitignore for excluding out direct...

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

[GitHub] kafka pull request #3268: KAFKA-5410: Fix taskClass() method name in Connect...

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

[jira] [Commented] (KAFKA-5410) Fix taskClass() method name in Connector and flush() signature in SinkTask

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

[GitHub] kafka pull request #3269: KAFKA-5410: Fix taskClass() method name in Connect...

GitHub user ppatierno opened a pull request: https://github.com/apache/kafka/pull/3269 KAFKA-5410: Fix taskClass() method name in Connector and flush() signature in SinkTask You can merge this pull request into a Git repository by running: $ git pull https://github.com/ppatie

[jira] [Commented] (KAFKA-5410) Fix taskClass() method name in Connector and flush() signature in SinkTask

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

[jira] [Created] (KAFKA-5411) Generate javadoc for AdminClient package

Ismael Juma created KAFKA-5411: -- Summary: Generate javadoc for AdminClient package Key: KAFKA-5411 URL: https://issues.apache.org/jira/browse/KAFKA-5411 Project: Kafka Issue Type: Improvement

[jira] [Commented] (KAFKA-5399) Crash Kafka & Zookeper with an basic Nmap Scan

[ https://issues.apache.org/jira/browse/KAFKA-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042619#comment-16042619 ] Rajini Sivaram commented on KAFKA-5399: --- [~morozov...@gmail.com] Thank you for repor

[jira] [Commented] (KAFKA-5401) Kafka Over TLS Error - Failed to send SSL Close message - Broken Pipe

[ https://issues.apache.org/jira/browse/KAFKA-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042627#comment-16042627 ] Rajini Sivaram commented on KAFKA-5401: --- This is a duplicate of KAFKA-3702. > Kafka

[GitHub] kafka pull request #3270: Fixed file URI path to log4j in bin/windows batch ...

GitHub user iotmani opened a pull request: https://github.com/apache/kafka/pull/3270 Fixed file URI path to log4j in bin/windows batch files Similar to what was done here, just more issues: https://github.com/apache/kafka/pull/3260 You can merge this pull request into a Git repo

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

[ https://issues.apache.org/jira/browse/KAFKA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5411: --- Description: Also fix the table of contents. > Generate javadoc for AdminClient and show configs in do

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

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

[VOTE] 0.11.0.0 RC0

Hello Kafka users, developers and client-developers, This is the first candidate for release of Apache Kafka 0.11.0.0. It's worth noting that there are a small number of unresolved issues (including documentation and system tests) related to the new AdminClient and Exactly-once functionality[1] th

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

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3271 KAFKA-5411: AdminClient javadoc and documentation improvements - Show AdminClient configs in the docs. - Update Javadoc config so that public classes exposed by the AdminClient are included.

[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&focusedCommentId=16042838#comment-16042838 ] ASF GitHub Bot commented on KAFKA-5411: --- GitHub user ijuma opened a pull request:

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

[ https://issues.apache.org/jira/browse/KAFKA-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5411: --- Status: Patch Available (was: Open) > Generate javadoc for AdminClient and show configs in documentat

[jira] [Updated] (KAFKA-5391) Replace zkClient.delete* method with an equivalent zkUtils method

[ https://issues.apache.org/jira/browse/KAFKA-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5391: --- Resolution: Fixed Fix Version/s: 0.11.1.0 Status: Resolved (was: Patch Available) I

[GitHub] kafka pull request #3245: KAFKA-5391 Replace zkClient.delete* method with an...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3245 --- 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-5391) Replace zkClient.delete* method with an equivalent zkUtils method

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

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

See Changes: [ismael] KAFKA-5391; Replace zkClient.delete* method with an equivalent zkUtills -- [...truncated 813.49 KB...] at com.sun.proxy.$Proxy70.onOutput(Unk

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

Paolo Patierno created KAFKA-5412: - Summary: Using connect-console-sink/source.properties raises an exception related to "file" property not found Key: KAFKA-5412 URL: https://issues.apache.org/jira/browse/KAFKA-5

[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&focusedCommentId=16043002#comment-16043002 ] Bharat Viswanadham commented on KAFKA-5409: --- Hi Paolo, There are 2 ways provided

[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&focusedCommentId=16043002#comment-16043002 ] Bharat Viswanadham edited comment on KAFKA-5409 at 6/8/17 4:44 PM: -

[jira] [Commented] (KAFKA-5246) Remove backdoor that allows any client to produce to internal topics

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

[GitHub] kafka pull request #3061: KAFKA-5246: Remove backdoor that allows any client...

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

[GitHub] kafka pull request #3261: MINOR: Set log level for producer internals to tra...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3261 --- 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-5246) Remove backdoor that allows any client to produce to internal topics

[ https://issues.apache.org/jira/browse/KAFKA-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Coates updated KAFKA-5246: --- Resolution: Won't Fix Status: Resolved (was: Patch Available) Discussions on PR mean we're cl

[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&focusedCommentId=16043018#comment-16043018 ] Randall Hauch commented on KAFKA-5412: -- I believe the proper correction would be to a

[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 connect-console-sin

[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&focusedCommentId=16043034#comment-16043034 ] Paolo Patierno commented on KAFKA-5412: --- Yes I agree this is a better solution. I'd

[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 Alternativ

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 incor

[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 Alternat

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 particular.

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 move the initializer and

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 aggregato

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 wrote: > Just brin

[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&focusedCommentId=16043185#comment-16043185 ] Paolo Patierno commented on KAFKA-5409: --- Hi Bharat, you are right but ... inside the

[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&focusedCommentId=16043185#comment-16043185 ] Paolo Patierno edited comment on KAFKA-5409 at 6/8/17 6:23 PM: -

[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:KIP-163: Lower the Minimum Required ACL Permission of OffsetFetch Hi, I

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 binding) > > > > Dong, thanks for the KI

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 point. I > have update

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 init

[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 enab

[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&focusedCommentId=16043233#comment-16043233 ] ASF GitHub Bot commented on KAFKA-5357: --- Github user asfgit closed the pull request

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

See

[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&focusedCommentId=16043268#comment-16043268 ] Bharat Viswanadham commented on KAFKA-5409: --- Hi Paolo, Ya missed that point. Ya

[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&focusedCommentId=16043329#comment-16043329 ] Viktor Somogyi commented on KAFKA-1044: --- @ewencp, thank you for your help. I've star

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...] org.apache.kafka.streams.integration.KStreamsFineGrainedAutoR

[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 enab

[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 enabl

[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 a

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 t

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

See Changes: [wangguoz] KAFKA-5357 follow-up: Yammer metrics, not Kafka Metrics -- [...truncated 4.58 MB...] org.apache.kafka.streams.integration.KStreamAggregationIntegr

[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 enab

[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 [https://github.com/apache/kafka/pull/3201

[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&focusedCommentId=16043446#comment-16043446 ] ASF GitHub Bot commented on KAFKA-5362: --- Github user asfgit closed the pull request

[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&focusedCommentId=16043458#comment-16043458 ] Colin P. McCabe commented on KAFKA-1955: As Jay wrote, there are some potential pr

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 >

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

See

[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&focusedCommentId=16043469#comment-16043469 ] Colin P. McCabe commented on KAFKA-3925: The issue with {{/var}} is that if you ru

[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&focusedCommentId=16043472#comment-16043472 ] Ismael Juma commented on KAFKA-3925: Unit tests set the log.dir explicitly so they wou

[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 update-delivery-semantics

[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}} a

[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 enable

[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 not

[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&focusedCommentId=16043480#comment-16043480 ] Jun Rao commented on KAFKA-5402: Not sure if this is the same as KAFKA-3980. Currently, if

[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&focusedCommentId=16043484#comment-16043484 ] Ji sun commented on KAFKA-3199: --- Hi Adam, do you mind me taking this jira for Kafka 0.10? >

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 dele

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 peop

[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&focusedCommentId=16043494#comment-16043494 ] Jay Kreps commented on KAFKA-1955: -- I think the patch I submitted was kind of a cool hack

[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&focusedCommentId=16043494#comment-16043494 ] Jay Kreps edited comment on KAFKA-1955 at 6/8/17 9:41 PM: -- I thin

[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&focusedCommentId=16043494#comment-16043494 ] Jay Kreps edited comment on KAFKA-1955 at 6/8/17 9:43 PM: -- I thin

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] [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&focusedCommentId=16043503#comment-16043503 ] Adam Kunicki commented on KAFKA-3199: - Yes, thank you! [~jisunkim] > LoginManager sho

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 agai

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

[ https://issues.apache.org/jira/browse/KAFKA-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043528#comment-16043528 ] Guozhang Wang commented on KAFKA-4628: -- [~dminkovsky] Thanks for sharing your use cas

[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&focusedCommentId=16043541#comment-16043541 ] Gwen Shapira commented on KAFKA-5317: - I understand the importance, but is it really a

[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 Alternat

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 no

[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 enab

[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)

[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&focusedCommentId=16043546#comment-16043546 ] ASF GitHub Bot commented on KAFKA-5411: --- Github user asfgit closed the pull request

[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 enab

[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 confi

[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&focusedCommentId=16043552#comment-16043552 ] ASF GitHub Bot commented on KAFKA-3199: --- GitHub user utenakr opened a pull request:

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

See

[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&focusedCommentId=16043562#comment-16043562 ] Ismael Juma commented on KAFKA-5317: Technically, it should be. > Update KIP-98 to re

  1   2   >