[jira] [Created] (KAFKA-5287) Messages getting repeated in kafka

Abhimanyu Nagrath created KAFKA-5287: Summary: Messages getting repeated in kafka Key: KAFKA-5287 URL: https://issues.apache.org/jira/browse/KAFKA-5287 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

Just copying in from the mail list, another use case / +1 for the builder pattern, so its kept with the KIP thread. On 18/05/2017, 22:06, "Andrew Coates" wrote: Thanks Mike On Thu, 18 May 2017 at 21:33, Michael André Pearce < michael.andre.pea...@me.com> wrote: >Hi Andrew,

Re: [DISCUSS] KIP 141 - ProducerRecordBuilder Interface

And I just failed at a basic copy/paste exercise (bangs head on wall) Try again: > On 18 May 2017, at 18:29, Andrew Coates wrote: > > Hi all, > > The `ProducerRecord` type has many optional fields and the list has grown over different revisions of Kafka. Kafka supports `ProducerInterceptor`s, w

[jira] [Assigned] (KAFKA-4868) Optimize RocksDb config for fast recovery/bulk load

[ https://issues.apache.org/jira/browse/KAFKA-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-4868: --- Assignee: Eno Thereska > Optimize RocksDb config for fast recovery/bulk load > --

[jira] [Updated] (KAFKA-4868) Optimize RocksDb config for fast recovery/bulk load

[ https://issues.apache.org/jira/browse/KAFKA-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4868: Priority: Major (was: Minor) > Optimize RocksDb config for fast recovery/bulk load > --

[jira] [Assigned] (KAFKA-4868) Optimize RocksDb config for fast recovery/bulk load

[ https://issues.apache.org/jira/browse/KAFKA-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska reassigned KAFKA-4868: --- Assignee: Bill Bejeck (was: Eno Thereska) > Optimize RocksDb config for fast recovery/bulk l

[jira] [Updated] (KAFKA-4868) Optimize RocksDb config for fast recovery/bulk load

[ https://issues.apache.org/jira/browse/KAFKA-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska updated KAFKA-4868: Fix Version/s: (was: 0.11.0.0) 0.11.1.0 > Optimize RocksDb config for fast re

[jira] [Commented] (KAFKA-4603) the argument of shell in doc wrong and command parsed error

[ https://issues.apache.org/jira/browse/KAFKA-4603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017046#comment-16017046 ] Xin commented on KAFKA-4603: [~guozhang][~ewencp] can you take a look at this issue? > the ar

[jira] [Commented] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017058#comment-16017058 ] Damian Guy commented on KAFKA-5063: --- Another instance of this failure: {noformat} java.l

[jira] [Reopened] (KAFKA-5063) Flaky ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic

[ https://issues.apache.org/jira/browse/KAFKA-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reopened KAFKA-5063: --- > Flaky > ResetIntegrationTest.testReprocessingFromScratchAfterResetWithIntermediateUserTopic > -

[jira] [Created] (KAFKA-5288) Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterResetWithoutIntermediateUserTopic

Damian Guy created KAFKA-5288: - Summary: Failure in org.apache.kafka.streams.integration.ResetIntegrationTest.testReprocessingFromScratchAfterResetWithoutIntermediateUserTopic Key: KAFKA-5288 URL: https://issues.apach

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi, I see you've removed the `ProcessorContext` from the RichFunction which is good, but why is it a `RichFunction`? I'd have expected it to pass some additional contextual information, i.e., the `RecordContext` that contains just the topic, partition, timestamp, offset. I'm ok with it not passin

[jira] [Created] (KAFKA-5289) One StopReplicaRequest will caused two Responses

xuzq created KAFKA-5289: --- Summary: One StopReplicaRequest will caused two Responses Key: KAFKA-5289 URL: https://issues.apache.org/jira/browse/KAFKA-5289 Project: Kafka Issue Type: Bug Compon

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuzq updated KAFKA-5289: Attachment: (was: 屏幕快照 2017-05-19 16.34.21.png) > One StopReplicaRequest will caused two Responses > ---

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuzq updated KAFKA-5289: Attachment: handleStopReplicaRequest.png > One StopReplicaRequest will caused two Responses > --

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuzq updated KAFKA-5289: Description: After discussed with my friend markTC，we find a bug. One StopReplicaRequest will caused two Responses.

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuzq updated KAFKA-5289: Description: After discussed with my friend markTC，we find a bug. One StopReplicaRequest will caused two Responses.

[jira] [Commented] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017075#comment-16017075 ] Ismael Juma commented on KAFKA-5289: Thanks for the report. Great catch. What kind of

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] xuzq updated KAFKA-5289: Description: After discussed with my friend markTC，we find a bug. One StopReplicaRequest will caused two Responses.

[jira] [Commented] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017098#comment-16017098 ] xuzq commented on KAFKA-5289: - We overwrote the ReplicaFetcherManager class, and threw an exc

[jira] [Comment Edited] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017098#comment-16017098 ] xuzq edited comment on KAFKA-5289 at 5/19/17 9:10 AM: -- We overwrote t

[GitHub] kafka pull request #3096: KAFKA-5289: handleStopReplica should not send a se...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3096 KAFKA-5289: handleStopReplica should not send a second response `shutdownIdleFetcherThreads()` can throw InterruptedException for example. You can merge this pull request into a Git repository by

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5289: --- Fix Version/s: 0.11.0.0 Status: Patch Available (was: Open) > One StopReplicaRequest will

[jira] [Commented] (KAFKA-5289) One StopReplicaRequest will caused two Responses

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

[jira] [Assigned] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-5289: -- Assignee: Ismael Juma > One StopReplicaRequest will caused two Responses >

[jira] [Commented] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017105#comment-16017105 ] xuzq commented on KAFKA-5289: - [~ijuma] Why not put the line 'requestChannel.sendResponse(new

[jira] [Updated] (KAFKA-4952) ZkUtils get topics by consumer group not correct

[ https://issues.apache.org/jira/browse/KAFKA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoXingyu updated KAFKA-4952: -- Attachment: (was: WechatIMG1.jpeg) > ZkUtils get topics by consumer group not correct >

[jira] [Resolved] (KAFKA-4952) ZkUtils get topics by consumer group not correct

[ https://issues.apache.org/jira/browse/KAFKA-4952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ZhaoXingyu resolved KAFKA-4952. --- Resolution: Invalid > ZkUtils get topics by consumer group not correct > -

[GitHub] kafka pull request #3095: MINOR: Bump Kafka version to 0.11.1.0-SNAPSHOT

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3095 --- 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-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017111#comment-16017111 ] Ma Tianchi commented on KAFKA-5289: --- I think the importation thing is not "What kind of

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

Kyle, it might make sense to start a VOTE thread, it doesn’t seem there are more comments. Thanks Eno > On May 16, 2017, at 6:42 PM, Damian Guy wrote: > > Yeah - i wish we'd named KGroupedStream GroupedKStream, similarly for > KGroupedTable. > > On Tue, 16 May 2017 at 17:59 Kyle Winkelman > w

Re: [DISCUSS]: KIP-149: Enabling key access in ValueTransformer, ValueMapper, and ValueJoiner

Hi Damian, Thanks for your comments. I think providing to users *interface* rather than *abstract class* should be preferred (Matthias also raised this issue ), anyway I changed the corresponding parts of KIP. Regarding with passing additional contextual information, I think it is a tradeoff, 1)

[jira] [Created] (KAFKA-5290) docs need clarification on meaning of 'committed' to the log

Edoardo Comar created KAFKA-5290: Summary: docs need clarification on meaning of 'committed' to the log Key: KAFKA-5290 URL: https://issues.apache.org/jira/browse/KAFKA-5290 Project: Kafka I

[jira] [Updated] (KAFKA-5290) docs need clarification on meaning of 'committed' to the log

[ https://issues.apache.org/jira/browse/KAFKA-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-5290: - Description: The docs around http://kafka.apache.org/documentation/#semantics http://kafka.apache.

[jira] [Updated] (KAFKA-5290) docs need clarification on meaning of 'committed' to the log

[ https://issues.apache.org/jira/browse/KAFKA-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edoardo Comar updated KAFKA-5290: - Description: The docs around http://kafka.apache.org/documentation/#semantics http://kafka.apache.

[jira] [Comment Edited] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017122#comment-16017122 ] Ismael Juma edited comment on KAFKA-5289 at 5/19/17 9:33 AM: -

[jira] [Commented] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017122#comment-16017122 ] Ismael Juma commented on KAFKA-5289: [~xuzq_zander], because we don't to delay the res

[jira] [Created] (KAFKA-5291) AdminClient should not trigger auto creation of topics

Ismael Juma created KAFKA-5291: -- Summary: AdminClient should not trigger auto creation of topics Key: KAFKA-5291 URL: https://issues.apache.org/jira/browse/KAFKA-5291 Project: Kafka Issue Type:

[GitHub] kafka pull request #3097: KAFKA-5134 Replace zkClient.getChildren method wit...

GitHub user baluchicken opened a pull request: https://github.com/apache/kafka/pull/3097 KAFKA-5134 Replace zkClient.getChildren method with zkUtils.getChildren @ijuma plz review. I also created a version where I didn't refactor the getPartitionAssignmentForTopics and the getConsum

[jira] [Commented] (KAFKA-5134) Replace zkClient.getChildren method with zkUtils.getChildren

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

[jira] [Commented] (KAFKA-4830) Augment KStream.print() to allow users pass in extra parameters in the printed string

[ https://issues.apache.org/jira/browse/KAFKA-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017189#comment-16017189 ] james chien commented on KAFKA-4830: [~mjsax] Okay, I will study about how to write it

[jira] [Updated] (KAFKA-5289) One StopReplicaRequest will caused two Responses

[ https://issues.apache.org/jira/browse/KAFKA-5289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ma Tianchi updated KAFKA-5289: -- Attachment: KAFKA-5289.patch just catch it > One StopReplicaRequest will caused two Responses > ---

[GitHub] kafka pull request #3098: KAFKA-5291: AdminClient should not trigger auto cr...

GitHub user ijuma opened a pull request: https://github.com/apache/kafka/pull/3098 KAFKA-5291: AdminClient should not trigger auto creation of topics - Added a boolean allow_auto_topic_creation to MetadataRequest. I didn’t bump the version a second time since we did it once for

[jira] [Commented] (KAFKA-5291) AdminClient should not trigger auto creation of topics

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

[jira] [Updated] (KAFKA-5291) AdminClient should not trigger auto creation of topics

[ https://issues.apache.org/jira/browse/KAFKA-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5291: --- Status: Patch Available (was: Open) > AdminClient should not trigger auto creation of topics > --

[GitHub] kafka pull request #3099: KAFKA-4660 : Improve test coverage KafkaStreams

GitHub user umesh9794 opened a pull request: https://github.com/apache/kafka/pull/3099 KAFKA-4660 : Improve test coverage KafkaStreams @dguy , @mjsax Please review the PR and let me know your comments. You can merge this pull request into a Git repository by running: $ git pul

[jira] [Commented] (KAFKA-4660) Improve test coverage KafkaStreams

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

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

See

[jira] [Assigned] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

[ https://issues.apache.org/jira/browse/KAFKA-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] huxi reassigned KAFKA-5278: --- Assignee: huxi > kafka-console-consumer: `--value-deserializer` is not working but `--property > value.deser

[GitHub] kafka pull request #3100: KAFKA-5278: Have console-consumer support `--value...

GitHub user amethystic opened a pull request: https://github.com/apache/kafka/pull/3100 KAFKA-5278: Have console-consumer support `--value-deserializer` In the original implementation, console-consumer fails to honor `--value-deserializer` config. You can merge this pull request in

[jira] [Commented] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

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

[Vote] KIP-150 - Kafka-Streams Cogroup

Hello all, I would like to start the vote on KIP-150. https://cwiki.apache.org/confluence/display/KAFKA/KIP-150+-+Kafka-Streams+Cogroup Thanks, Kyle

[jira] [Created] (KAFKA-5292) Authorization tests for AdminClient

Ismael Juma created KAFKA-5292: -- Summary: Authorization tests for AdminClient Key: KAFKA-5292 URL: https://issues.apache.org/jira/browse/KAFKA-5292 Project: Kafka Issue Type: Sub-task

Re: [VOTE] KIP-117: Add a public AdminClient API for Kafka admin operations

Hi all, Feedback from people who tried the AdminClient is that auto topic creation during describe is unexpected and confusing. This is consistent with the reaction of most people when they learn that MetadataRequest can cause topics to be created. We had assumed that we'd tackle this issue for al

[jira] [Assigned] (KAFKA-5154) Kafka Streams throws NPE during rebalance

[ https://issues.apache.org/jira/browse/KAFKA-5154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy reassigned KAFKA-5154: - Assignee: Damian Guy (was: Matthias J. Sax) > Kafka Streams throws NPE during rebalance > --

[jira] [Updated] (KAFKA-3878) Exponential backoff for broker reconnect attempts

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

[GitHub] kafka pull request #1523: KAFKA-3878: Support exponential backoff policy via...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/1523 --- 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-3878) Exponential backoff for broker reconnect attempts

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

[jira] [Updated] (KAFKA-3878) Exponential backoff for broker reconnect attempts (KIP-144)

[ https://issues.apache.org/jira/browse/KAFKA-3878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3878: --- Summary: Exponential backoff for broker reconnect attempts (KIP-144) (was: Exponential backoff for br

[jira] [Created] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

Ismael Juma created KAFKA-5293: -- Summary: Do not apply exponential backoff if users have overridden reconnect.backoff.ms Key: KAFKA-5293 URL: https://issues.apache.org/jira/browse/KAFKA-5293 Project: Kaf

[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5293: --- Description: The PR for KAFKA-3878 implemented KIP-144 with one exception: it automatically enables e

[jira] [Updated] (KAFKA-5293) Do not apply exponential backoff if users have overridden reconnect.backoff.ms

[ https://issues.apache.org/jira/browse/KAFKA-5293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5293: --- Issue Type: Bug (was: Improvement) > Do not apply exponential backoff if users have overridden reconn

[jira] [Commented] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017431#comment-16017431 ] anugrah commented on KAFKA-5245: sure. I will start on this. > KStream builder should cap

[jira] [Assigned] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] anugrah reassigned KAFKA-5245: -- Assignee: anugrah > KStream builder should capture serdes > -- > >

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

See Changes: [ismael] KAFKA-3878; Support exponential backoff policy via reconnect.backoff.max -- [...truncated 886.37 KB...] kafka.controller.ControllerIntegrationTest >

[GitHub] kafka pull request #3101: KAFKA-5279: TransactionCoordinator must expire tra...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3101 KAFKA-5279: TransactionCoordinator must expire transactionalIds remove transactions that have not been updated for at least `transactional.id.expiration.ms` You can merge this pull request into a Git

[jira] [Commented] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

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

[jira] [Updated] (KAFKA-5279) TransactionCoordinator must expire transactionalIds

[ https://issues.apache.org/jira/browse/KAFKA-5279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damian Guy updated KAFKA-5279: -- Status: Patch Available (was: Open) > TransactionCoordinator must expire transactionalIds > ---

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

See

Bug Submit - Critical

Hello, I have no idea how to submit a bug : amongst all the help given to participate to the project, submitting a bug is the hardest and least documented, neither is easy to do. So I hope this email will reach the proper hands on your side :-) The bug is easy to reproduce: 1 - Create a topic wi

Re: Bug Submit - Critical

Hi Fabien, This has already been fixed, see: https://issues.apache.org/jira/browse/KAFKA-5232 https://github.com/apache/kafka/commit/f56bbb6510df8c12db3ad075e2f6c78dd0092d60 https://github.com/apache/kafka/commit/1ca2b1aacc2994e441c1a949310129d3e78532b5 To file issues in the future, please go to

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

This sounds like https://issues.apache.org/jira/browse/KAFKA-5232. It’s been fixed a few days back in upstream and will be available in next releases. Having said that, you note something about split() method which wasn’t applicable here. Which version of Kafka are you on? Can you paste the comp

[jira] [Commented] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)

[ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017475#comment-16017475 ] Jorge Quilcate commented on KAFKA-5266: --- [~hachikuji] some comments about the improv

Re: Bug Submit - Critical

Fixing the subject line in my previous reply. Not sure what happened there. -Jaikiran On 19-May-2017, at 8:06 PM, J Pai wrote: This sounds like https://issues.apache.org/jira/browse/KAFKA-5232. It’s been fixed a few days back in upstream and will be available in next releases. Having said that

[GitHub] kafka pull request #3102: Implement Improvements

GitHub user jeqo opened a pull request: https://github.com/apache/kafka/pull/3102 Implement Improvements Implement improvements defined here: https://issues.apache.org/jira/browse/KAFKA-5266 You can merge this pull request into a Git repository by running: $ git pull https://g

[jira] [Commented] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122)

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

[jira] [Created] (KAFKA-5295) Allow Kafka Connect source connectors to specify topic-specific settings for new topics

Randall Hauch created KAFKA-5295: Summary: Allow Kafka Connect source connectors to specify topic-specific settings for new topics Key: KAFKA-5295 URL: https://issues.apache.org/jira/browse/KAFKA-5295

[jira] [Created] (KAFKA-5294) PlainSaslServerFactory should allow a null Map in getMechanismNames

Bryan Bende created KAFKA-5294: -- Summary: PlainSaslServerFactory should allow a null Map in getMechanismNames Key: KAFKA-5294 URL: https://issues.apache.org/jira/browse/KAFKA-5294 Project: Kafka

[jira] [Commented] (KAFKA-5294) PlainSaslServerFactory should allow a null Map in getMechanismNames

[ https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017505#comment-16017505 ] Ismael Juma commented on KAFKA-5294: Thanks for the report. This is a simple fix, so w

[jira] [Updated] (KAFKA-5294) PlainSaslServerFactory should allow a null Map in getMechanismNames

[ https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5294: --- Fix Version/s: 0.11.0.0 > PlainSaslServerFactory should allow a null Map in getMechanismNames > --

[jira] [Updated] (KAFKA-5294) PlainSaslServerFactory should allow a null Map in getMechanismNames

[ https://issues.apache.org/jira/browse/KAFKA-5294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-5294: --- Priority: Major (was: Minor) > PlainSaslServerFactory should allow a null Map in getMechanismNames >

[jira] [Comment Edited] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

[ https://issues.apache.org/jira/browse/KAFKA-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017556#comment-16017556 ] Vahid Hashemian edited comment on KAFKA-5278 at 5/19/17 3:38 PM: ---

[jira] [Commented] (KAFKA-5278) kafka-console-consumer: `--value-deserializer` is not working but `--property value.deserializer` does

[ https://issues.apache.org/jira/browse/KAFKA-5278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017556#comment-16017556 ] Vahid Hashemian commented on KAFKA-5278: Looks like the issue reported here is a s

[jira] [Commented] (KAFKA-5128) TransactionCoordinator - Check inter broker protocol and message format and raise errors if incompatible

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

[GitHub] kafka pull request #3103: KAFKA-5128: check inter broker and message format ...

GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/3103 KAFKA-5128: check inter broker and message format versions in transactional methods [WIP] Add check in `KafkaApis` that the inter broker protocol and message format versions are at least `KAFKA_0_11_0

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

Sorry to jump on this thread so late. I agree this is a very useful addition and wanted to provide an additional use-case and some more comments. This is actually a very common analytics use-case in the ad-tech industry. The typical setup will have an auction stream, an impression stream, and a cl

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

Hi Kyle, I left a few more comments in the discussion thread, if you wouldn't mind taking a look On Fri, May 19, 2017 at 5:31 AM Kyle Winkelman wrote: > Hello all, > > I would like to start the vote on KIP-150. > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-150+-+Kafka-Streams+Cogroup

[jira] [Commented] (KAFKA-4785) Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor

[ https://issues.apache.org/jira/browse/KAFKA-4785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017575#comment-16017575 ] Jeyhun Karimov commented on KAFKA-4785: --- [~mjsax] Thanks for reminding. I am on it

Re: KTable aggregate corruption on poorly timed exception

Whoops, I said I'd put the specific exception at the bottom of the e-mail. It probably isn't the important part of this thread, but might suggest when this situation can occur. Also of note, this is occurring on Kafka Streams 0.10.2.1. 20:56:07.061 [StreamThread-3] ERROR o.a.k.s.p.internals.Str

KTable aggregate corruption on poorly timed exception

Hi Kafka devs, This morning I observed a specific Kafka Streams aggregation that ended up with an incorrect computed output after a Kafka Streams thread crashed with an unhandled exception. The topology is pretty simple -- a single KTable source, group by a field in the value, aggregate that adds

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017626#comment-16017626 ] Colin P. McCabe commented on KAFKA-5275: bq. [~rhauch]: Also, a common use case fo

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017629#comment-16017629 ] Colin P. McCabe commented on KAFKA-5275: bq. It'd be great to simplify the creatio

[jira] [Comment Edited] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017629#comment-16017629 ] Colin P. McCabe edited comment on KAFKA-5275 at 5/19/17 4:37 PM: ---

[jira] [Commented] (KAFKA-5291) AdminClient should not trigger auto creation of topics

[ https://issues.apache.org/jira/browse/KAFKA-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017637#comment-16017637 ] Ismael Juma commented on KAFKA-5291: cc [~cmccabe] > AdminClient should not trigger a

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017646#comment-16017646 ] Xavier Léauté commented on KAFKA-5275: -- Speaking of {{TopicExistsException}} it would

[jira] [Commented] (KAFKA-5275) Review and potentially tweak AdminClient API for the initial release (KIP-117)

[ https://issues.apache.org/jira/browse/KAFKA-5275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017659#comment-16017659 ] Xavier Léauté commented on KAFKA-5275: -- To echo Randall's point about having a topic

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

I like your point about not handling other cases such as count and reduce. I think that reduce may not make sense because reduce assumes that the input values are the same as the output values. With cogroup there may be multiple different input types and then your output type cant be multiple diff

Re: Reg: [VOTE] KIP 157 - Add consumer config options to streams reset tool

I double checked with Matthew Warhaftig (the original author of KIP-14) and he has not interest to continue the KIP atm. Thus, Bharat can continue the work on KIP-14. I think it would be best, to start a new DISCUSS thread after you update KIP-14. Thanks for your contributions! -Matthias On 5

Re: Reg: [VOTE] KIP 157 - Add consumer config options to streams reset tool

Hi Matthias, I will start a new KIP for Kafka tools options to be a standard across all tools shortly. But I think the KIP 157 for Kafka Streams, should be needed for 0.11.0.0 release, (KIP freeze date is already over, but I think this is minor code change in tools to add option to streams reset to

[jira] [Commented] (KAFKA-5117) Kafka Connect REST endpoints reveal Password typed values

[ https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017689#comment-16017689 ] Thomas Holmes commented on KAFKA-5117: -- I had some code that seems to work but I'm no

  1   2   >