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

[ https://issues.apache.org/jira/browse/KAFKA-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4660: --- Status: Patch Available (was: Open) > Improve test coverage KafkaStreams > --

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

KIP-157 cannot be included in 0.11.0.0 anymore. KIP freeze date deadline is strict. -Matthias On 5/19/17 10:15 AM, BigData dev wrote: > 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 n

[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=16017701#comment-16017701 ] Randall Hauch commented on KAFKA-5275: -- [~colinmccabe] wrote: {quote} We could add a

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

Thanks for the info, Matthias. Regards, Bharat On Fri, May 19, 2017 at 10:25 AM, Matthias J. Sax wrote: > KIP-157 cannot be included in 0.11.0.0 anymore. KIP freeze date deadline > is strict. > > -Matthias > > On 5/19/17 10:15 AM, BigData dev wrote: > > Hi Matthias, > > I will start a new KIP

[GitHub] kafka pull request #3065: KAFKA-4714: TimestampConverter transformation (KIP...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3065 --- 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-4714) Implement remaining KIP-66 SMTs

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

[GitHub] kafka pull request #3104: MINOR: improve EmbeddedKafkaCluster test utility f...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3104 MINOR: improve EmbeddedKafkaCluster test utility for deleting topics You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka minor-improve-em

[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=16017870#comment-16017870 ] Jason Gustafson commented on KAFKA-5266: [~jeqo] Thanks for explaining the case fo

[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017884#comment-16017884 ] kyle k commented on KAFKA-3821: --- As a potential solution why can't the {{OffsetStorageWriter

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

See Changes: [jason] KAFKA-4714; TimestampConverter transformation (KIP-66) -- [...truncated 883.70 KB...] kafka.security.auth.SimpleAclAuthorizerTest > testTopicAcl START

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

See

[GitHub] kafka pull request #3105: KAFKA-5294: PlainSaslServerFactory should allow a ...

GitHub user mimaison opened a pull request: https://github.com/apache/kafka/pull/3105 KAFKA-5294: PlainSaslServerFactory should allow a null Map in getMech… …anismNames If props is null, use POLICY_NOPLAINTEXT default value: false As far as I can tell, none of t

[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=16017935#comment-16017935 ] ASF GitHub Bot commented on KAFKA-5294: --- GitHub user mimaison opened a pull request:

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

With the current KIP, using ValueMapper and ValueMapperWithKey interfaces, RichFunction seems to be an independent add-on. To fix the original issue to allow key access, RichFunctions are not required IMHO. I initially put the RichFunction idea on the table, because I was hoping to get a uniform A

[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=16018004#comment-16018004 ] Jorge Quilcate commented on KAFKA-5266: --- [~hachikuji] Thanks! For case 3, maybe `--

[jira] [Comment Edited] (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=16018004#comment-16018004 ] Jorge Quilcate edited comment on KAFKA-5266 at 5/19/17 9:04 PM:

[jira] [Work started] (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:all-tabpanel ] Work on KAFKA-5266 started by Jorge Quilcate. - > Follow-up improvements for consumer offset reset tool (KIP-122) > ---

Re: KTable aggregate corruption on poorly timed exception

Hi Mathieu, Thanks for reporting this! This is definitely a bug and it must get fixed for at-last-once processing, too. Exactly-once is not required to avoid the bug. Can you open a Jira? I think, I know already how to fix it. -Matthias On 5/19/17 8:53 AM, Mathieu Fenniak wrote: > Whoops, I

[jira] [Commented] (KAFKA-5191) Autogenerate Consumer Fetcher metrics

[ https://issues.apache.org/jira/browse/KAFKA-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018069#comment-16018069 ] James Cheng commented on KAFKA-5191: Pinging [~ijuma] [~hachikuji] [~benstopford] for

[GitHub] kafka pull request #3106: KAFKA-4785: Records from internal repartitioning t...

GitHub user jeyhunkarimov opened a pull request: https://github.com/apache/kafka/pull/3106 KAFKA-4785: Records from internal repartitioning topics should always use RecordMetadataTimestampExtractor You can merge this pull request into a Git repository by running: $ git pull h

[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=16018071#comment-16018071 ] ASF GitHub Bot commented on KAFKA-4785: --- GitHub user jeyhunkarimov opened a pull req

[GitHub] kafka pull request #3107: MINOR: improve descriptions of Streams reset tool ...

GitHub user mjsax opened a pull request: https://github.com/apache/kafka/pull/3107 MINOR: improve descriptions of Streams reset tool options You can merge this pull request into a Git repository by running: $ git pull https://github.com/mjsax/kafka minor-reset-tool-options Al

[jira] [Work started] (KAFKA-5259) TransactionalId authorization should imply ProducerId authorization

[ https://issues.apache.org/jira/browse/KAFKA-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-5259 started by Jason Gustafson. -- > TransactionalId authorization should imply ProducerId authorization > -

[jira] [Updated] (KAFKA-5259) TransactionalId authorization should imply ProducerId authorization

[ https://issues.apache.org/jira/browse/KAFKA-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5259: --- Status: Patch Available (was: In Progress) > TransactionalId authorization should imply Produ

[jira] [Comment Edited] (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=16018106#comment-16018106 ] Jason Gustafson edited comment on KAFKA-5266 at 5/19/17 10:14 PM: --

[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=16018106#comment-16018106 ] Jason Gustafson commented on KAFKA-5266: [~jeqo] Maybe it could be "--to-current,"

[jira] [Updated] (KAFKA-5269) TransactionBounceTest occasionally fails due to partition errors

[ https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5269: Status: Patch Available (was: Open) > TransactionBounceTest occasionally fails due to partition err

[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=16018135#comment-16018135 ] Matthias J. Sax commented on KAFKA-5063: [~damianguy] The error you report is a di

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

Couple of follow ups. The reset tool uses AdminClient, ZkUtils, and a KafkaConsumer internally. Thus, I am wondering if we need the possibility to specify configs for all of them? The original JIRA reported, that the reset tool does not work for a secured cluster, and thus, I doubt that consumer

[GitHub] kafka pull request #3107: MINOR: improve descriptions of Streams reset tool ...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3107 --- 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 #3108: KAFKA-5247: Materialize committed offsets in offse...

GitHub user apurvam opened a pull request: https://github.com/apache/kafka/pull/3108 KAFKA-5247: Materialize committed offsets in offset order With this patch, offset commits are always materialized according to the order of the commit records in the offsets topic. Before

[jira] [Updated] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

[ https://issues.apache.org/jira/browse/KAFKA-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apurva Mehta updated KAFKA-5247: Status: Patch Available (was: Open) > Consumer GroupCoordinator should continue to materialize comm

[jira] [Commented] (KAFKA-5247) Consumer GroupCoordinator should continue to materialize committed offsets in offset order even for transactional offset commits

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

[jira] [Created] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

Abhisek Saikia created KAFKA-5296: - Summary: Unable to write to some partitions of newly created topic in 10.2 Key: KAFKA-5296 URL: https://issues.apache.org/jira/browse/KAFKA-5296 Project: Kafka

[jira] [Updated] (KAFKA-5296) Unable to write to some partitions of newly created topic in 10.2

[ https://issues.apache.org/jira/browse/KAFKA-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhisek Saikia updated KAFKA-5296: -- Description: We are using kafka 10.2 and the cluster was running fine for a month with 50 topic

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

See

[GitHub] kafka pull request #3094: KAFKA-5269: Correct handling of UNKNOWN_TOPIC_OR_P...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/3094 --- 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-5269) TransactionBounceTest occasionally fails due to partition errors

[ https://issues.apache.org/jira/browse/KAFKA-5269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-5269: --- Resolution: Fixed Fix Version/s: 0.11.0.0 Status: Resolved (was: Patch Avail

[jira] [Commented] (KAFKA-5269) TransactionBounceTest occasionally fails due to partition errors

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

<    1   2