[jira] [Commented] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

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

[GitHub] kafka pull request #1547: KAFKA-3594; After calling MemoryRecords.close() me...

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

Re: [VOTE] KIP-4 Delete Topics Schema

+1

[jira] [Updated] (KAFKA-3594) Kafka new producer retries doesn't work in 0.9.0.1

[ https://issues.apache.org/jira/browse/KAFKA-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3594: --- Fix Version/s: 0.9.0.2 > Kafka new producer retries doesn't work in 0.9.0.1 >

[jira] [Commented] (KAFKA-3899) Consumer.poll() stuck in loop if wrong credentials are supplied

[ https://issues.apache.org/jira/browse/KAFKA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348172#comment-15348172 ] Edoardo Comar commented on KAFKA-3899: -- The Producer is instead more protected against these issues.

[jira] [Created] (KAFKA-3899) Consumer.poll() stuck in loop if wrong credentials are supplied

Edoardo Comar created KAFKA-3899: Summary: Consumer.poll() stuck in loop if wrong credentials are supplied Key: KAFKA-3899 URL: https://issues.apache.org/jira/browse/KAFKA-3899 Project: Kafka

[jira] [Commented] (KAFKA-3899) Consumer.poll() stuck in loop if wrong credentials are supplied

[ https://issues.apache.org/jira/browse/KAFKA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348181#comment-15348181 ] Edoardo Comar commented on KAFKA-3899: -- Like in the case of issue

[jira] [Updated] (KAFKA-3899) Consumer.poll() stuck in loop if wrong credentials are supplied

[ https://issues.apache.org/jira/browse/KAFKA-3899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-3899: - Affects Version/s: 0.10.1.0 > Consumer.poll() stuck in loop if wrong credentials are supplied >

Build failed in Jenkins: kafka_0.9.0_jdk7 #135

See Changes: [ismael] KAFKA-3594; After calling MemoryRecords.close() method, hasRoomFor() -- [...truncated 4254 lines...] kafka.utils.SchedulerTest > testRestart PASSED

[jira] [Created] (KAFKA-3900) High CPU util on broker

Andrey Konyaev created KAFKA-3900: - Summary: High CPU util on broker Key: KAFKA-3900 URL: https://issues.apache.org/jira/browse/KAFKA-3900 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-3892) Clients retain metadata for non-subscribed topics

[ https://issues.apache.org/jira/browse/KAFKA-3892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348426#comment-15348426 ] Noah Sloan commented on KAFKA-3892: --- [~ijuma] [~hachikuji] can you tell me what I need to do to move

[jira] [Commented] (KAFKA-3296) All consumer reads hang indefinately

[ https://issues.apache.org/jira/browse/KAFKA-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348485#comment-15348485 ] Piotr Trzpil commented on KAFKA-3296: - I can successfully reproduce this issue in AWS EC2, running

Re: [VOTE] KIP-4 Delete Topics Schema

+1 On Thu, Jun 23, 2016 at 8:32 PM, Grant Henke wrote: > I would like to initiate the voting process for the "KIP-4 Delete Topics > Schema changes". This is not a vote for all of KIP-4, but specifically for > the delete topics changes. I have included the exact changes

Re: [VOTE] KIP-4 Delete Topics Schema

+1 On Fri, Jun 24, 2016 at 9:52 AM, Jay Kreps wrote: > +1 > > On Thu, Jun 23, 2016 at 8:32 PM, Grant Henke wrote: > > > I would like to initiate the voting process for the "KIP-4 Delete Topics > > Schema changes". This is not a vote for all of KIP-4, but

[VOTE] KIP-65 Expose timestamps to Connect

Since there isn't much to discuss with this KIP, bringing it to a vote KIP: https://cwiki.apache.org/confluence/display/KAFKA/KIP-65%3A+Expose+timestamps+to+Connect Pull request: https://github.com/apache/kafka/pull/1537 Thanks, Shikhar

Re: [VOTE] KIP-65 Expose timestamps to Connect

+1 On Fri, Jun 24, 2016 at 10:59 AM, Shikhar Bhushan wrote: > Since there isn't much to discuss with this KIP, bringing it to a vote > > KIP: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-65%3A+Expose+timestamps+to+Connect > > Pull request:

[GitHub] kafka pull request #1550: MINOR: Improve doc string in PartitionGrouper

GitHub user guozhangwang opened a pull request: https://github.com/apache/kafka/pull/1550 MINOR: Improve doc string in PartitionGrouper You can merge this pull request into a Git repository by running: $ git pull https://github.com/guozhangwang/kafka

[jira] [Updated] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

[ https://issues.apache.org/jira/browse/KAFKA-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-3896: -- Assignee: Damian Guy > Unstable test >

[jira] [Commented] (KAFKA-3896) Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations

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

[GitHub] kafka pull request #1549: KAFKA-3896: Unstable test KStreamRepartitionJoinTe...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1549 KAFKA-3896: Unstable test KStreamRepartitionJoinTest.shouldCorrectlyRepartitionOnJoinOperations @ijuma i checked the cases where this test has failed and it seems to always be on the verification of

Re: [VOTE] KIP-4 Delete Topics Schema

+1 On Thu, Jun 23, 2016 at 8:32 PM, Grant Henke wrote: > I would like to initiate the voting process for the "KIP-4 Delete Topics > Schema changes". This is not a vote for all of KIP-4, but specifically for > the delete topics changes. I have included the exact changes

[jira] [Created] (KAFKA-3898) KStream.leftJoin(...) is missing a Serde for thisVal. This can cause failures after mapValues etc

Damian Guy created KAFKA-3898: - Summary: KStream.leftJoin(...) is missing a Serde for thisVal. This can cause failures after mapValues etc Key: KAFKA-3898 URL: https://issues.apache.org/jira/browse/KAFKA-3898

[jira] [Commented] (KAFKA-3898) KStream.leftJoin(...) is missing a Serde for thisVal. This can cause failures after mapValues etc

[ https://issues.apache.org/jira/browse/KAFKA-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347901#comment-15347901 ] Damian Guy commented on KAFKA-3898: --- If the stream has been mapped or flatMapped it needs the Serdes

Re: [DISCUSS] KIP-50 - Enhance Authorizer interface to be aware of supported Principal Types

I'm really late to this thread, but I want to propose a small change: what if we changed the proposed package for the authorizer from `org.apache.kafka.common.security.auth` to `org.apache.kafka.server.security.auth` (while still living in the `clients` jar)? The advantages are: 1. It would be

[jira] [Commented] (KAFKA-3898) KStream.leftJoin(...) is missing a Serde for thisVal. This can cause failures after mapValues etc

[ https://issues.apache.org/jira/browse/KAFKA-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347928#comment-15347928 ] Damian Guy commented on KAFKA-3898: --- Turns out this is not an issue on 0.10.0 - my mistake. It was an

[jira] [Resolved] (KAFKA-3898) KStream.leftJoin(...) is missing a Serde for thisVal. This can cause failures after mapValues etc

[ https://issues.apache.org/jira/browse/KAFKA-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy resolved KAFKA-3898. --- Resolution: Not A Problem > KStream.leftJoin(...) is missing a Serde for thisVal. This can cause

[GitHub] kafka pull request #1551: MINOR: fix grammatical errors in DataException mes...

GitHub user LaurierMantel opened a pull request: https://github.com/apache/kafka/pull/1551 MINOR: fix grammatical errors in DataException message Was just reading kafka source code, my favourite Friday afternoon activity, when I found these small grammatical errors in some

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

[ https://issues.apache.org/jira/browse/KAFKA-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3842: - Resolution: Fixed Status: Resolved (was: Patch Available) > Add Helper Functions Into

[GitHub] kafka pull request #1550: MINOR: Improve doc string in PartitionGrouper

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1550 --- 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 #1551: MINOR: fix grammatical errors in DataException mes...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1551 --- 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 #1552: MINOR: Typo fix in docs ops

GitHub user thanasis00 opened a pull request: https://github.com/apache/kafka/pull/1552 MINOR: Typo fix in docs ops You can merge this pull request into a Git repository by running: $ git pull https://github.com/thanasis00/kafka trunk Alternatively you can review and apply

Re: KTable.filter usage, memory consumption and materialized view semantics

Hello Philippe, Very good points, let me dump my thoughts about "KTable.filter" specifically and how we can improve on that: 1. Some context: when a KTable participates in a downstream operators (e.g. if that operator is an aggregation), then we need to materialize this KTable and send both its

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

[ https://issues.apache.org/jira/browse/KAFKA-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348603#comment-15348603 ] Guozhang Wang commented on KAFKA-3842: -- It is resolved as part of

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

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

[jira] [Created] (KAFKA-3901) KStreamTransformValues$KStreamTransformValuesProcessor#process() forwards null values

Dmitry Minkovsky created KAFKA-3901: --- Summary: KStreamTransformValues$KStreamTransformValuesProcessor#process() forwards null values Key: KAFKA-3901 URL: https://issues.apache.org/jira/browse/KAFKA-3901

Re: [VOTE] KIP-65 Expose timestamps to Connect

+1 On Fri, Jun 24, 2016 at 10:59 AM, Shikhar Bhushan wrote: > Since there isn't much to discuss with this KIP, bringing it to a vote > > KIP: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-65%3A+Expose+timestamps+to+Connect > > Pull request:

Re: [VOTE] KIP-65 Expose timestamps to Connect

+1 (binding), provided that we make the usage of `Long/null` versus `long/-1` consistent. Ismael On Sat, Jun 25, 2016 at 12:42 AM, Gwen Shapira wrote: > +1 > > On Fri, Jun 24, 2016 at 10:59 AM, Shikhar Bhushan > wrote: > > Since there isn't much to

Re: KTable.filter usage, memory consumption and materialized view semantics

Yes, it looks very good. Your detailed explanation appears compelling enough to reveal that some of the details of the complexity of a streams system are probably inherent complexity (not that I dared assume it was "easy" but I could afford to be conveniently unaware). It took me 30 minutes to

Re: [VOTE] KIP-65 Expose timestamps to Connect

+1 (non-binding) On Fri, Jun 24, 2016 at 11:26 AM, Jay Kreps wrote: > +1 > > On Fri, Jun 24, 2016 at 10:59 AM, Shikhar Bhushan > wrote: > > > Since there isn't much to discuss with this KIP, bringing it to a vote > > > > KIP: > > > > >

Re: [VOTE] KIP-65 Expose timestamps to Connect

+1 On Fri, Jun 24, 2016 at 3:03 PM, Jason Gustafson wrote: > +1 (non-binding) > > On Fri, Jun 24, 2016 at 11:26 AM, Jay Kreps wrote: > > > +1 > > > > On Fri, Jun 24, 2016 at 10:59 AM, Shikhar Bhushan > > wrote: > > > > > Since there

Re: [DISCUSS] KIP-65 Expose timestamps to Connect

Hi Shikhar, Thanks for the KIP. One question: SinkRecord takes a `long` timestamp, but then exposes it via a method that returns `Long`. Is this correct? And if so, can you please explain the reasoning? Ismael On Thu, Jun 23, 2016 at 8:06 PM, Shikhar Bhushan wrote: >

Re: [DISCUSS] KIP-65 Expose timestamps to Connect

Yes, I agree that it would be better to be consistent. I suggest `Long` and `null` everywhere if feasible as it's less opaque than the magic -1L value. The KIP page should be updated with what you decide. Ismael On Sat, Jun 25, 2016 at 1:29 AM, Shikhar Bhushan wrote: > Hi

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

See Changes: [wangguoz] KAFKA-3842: consolidate utility methods to TestUtils -- [...truncated 8176 lines...] org.apache.kafka.common.utils.UtilsTest > testGetHost STARTED

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

See

Re: [DISCUSS] KIP-65 Expose timestamps to Connect

Hi Ismael, Good point. This is down to an implementation detail, the getter was added to the base class for `SourceRecord` and `SinkRecord`, `ConnectRecord`. `SourceRecord` is treating missing timestamps as null while `SinkRecord` is treating it as the default value `Record.NO_TIMESTAMP` (-1L).

Re: [VOTE] KIP-4 Delete Topics Schema

+1 On Thu, Jun 23, 2016 at 8:32 PM, Grant Henke wrote: > I would like to initiate the voting process for the "KIP-4 Delete Topics > Schema changes". This is not a vote for all of KIP-4, but specifically for > the delete topics changes. I have included the exact changes below

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

See Changes: [wangguoz] KAFKA-3842: consolidate utility methods to TestUtils [me] MINOR: fix grammatical errors in DataException message -- [...truncated 11355 lines...]

[jira] [Commented] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15349058#comment-15349058 ] James Cheng commented on KAFKA-3480: Thanks [~hachikuji]! I'll flesh out the proof of concept some

[jira] [Updated] (KAFKA-3902) Optimize KTable.filter() to reduce unnecessary traffic

[ https://issues.apache.org/jira/browse/KAFKA-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3902: - Description: {{KTable.filter()}} operator is implemented in {{KTableFilter}}, and can be

[jira] [Created] (KAFKA-3902) Optimize KTable.filter() to reduce unnecessary traffic

Guozhang Wang created KAFKA-3902: Summary: Optimize KTable.filter() to reduce unnecessary traffic Key: KAFKA-3902 URL: https://issues.apache.org/jira/browse/KAFKA-3902 Project: Kafka Issue

Re: KTable.filter usage, memory consumption and materialized view semantics

Hi Philippe, Great, since you agree with my reasonings, I have created a JIRA ticket for optimizing KTableFilter (feel free to pick it up if you are interested in contributing): https://issues.apache.org/jira/browse/KAFKA-3902 About case 3-c-1), what I meant is that since "predicate return true

[jira] [Updated] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Cheng updated KAFKA-3480: --- Reviewer: (was: Jason Gustafson) Status: Open (was: Patch Available) > Autogenerate metrics

[jira] [Work started] (KAFKA-3480) Autogenerate metrics documentation

[ https://issues.apache.org/jira/browse/KAFKA-3480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3480 started by James Cheng. -- > Autogenerate metrics documentation > -- > >

[jira] [Updated] (KAFKA-3902) Optimize KTable.filter() to reduce unnecessary traffic

[ https://issues.apache.org/jira/browse/KAFKA-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-3902: - Description: {{KTable.filter()}} operator is implemented in {{KTableFilter}}, and can be

[jira] [Commented] (KAFKA-3901) KStreamTransformValues$KStreamTransformValuesProcessor#process() forwards null values

[ https://issues.apache.org/jira/browse/KAFKA-3901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15348624#comment-15348624 ] Dmitry Minkovsky commented on KAFKA-3901: - ...and