[jira] [Created] (KAFKA-6922) Rethink WindowedStreamPartitioner configurations

Guozhang Wang created KAFKA-6922: Summary: Rethink WindowedStreamPartitioner configurations Key: KAFKA-6922 URL: https://issues.apache.org/jira/browse/KAFKA-6922 Project: Kafka Issue Type: Im

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

See Changes: [wangguoz] KAFKA-6905: Document that Transformers may be re-used by Streams (#5026) -- [...truncated 421.25 KB...] kafka.zookeeper.ZooKeeperClientTest > test

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

See Changes: [wangguoz] KAFKA-6905: Document that Transformers may be re-used by Streams (#5026) -- [...truncated 425.39 KB...] kafka.utils.json.JsonValueTest > testDeco

[jira] [Created] (KAFKA-6921) Remove old Scala producer and all related code, tests, and tools

Ismael Juma created KAFKA-6921: -- Summary: Remove old Scala producer and all related code, tests, and tools Key: KAFKA-6921 URL: https://issues.apache.org/jira/browse/KAFKA-6921 Project: Kafka I

Build failed in Jenkins: kafka-trunk-jdk10 #117

See Changes: [wangguoz] KAFKA-6905: Document that Transformers may be re-used by Streams (#5026) -- [...truncated 1.50 MB...] kafka.utils.json.JsonValueTest > testAsJsonO

[jira] [Created] (KAFKA-6920) Enhance ConsumerRecordFactory and OutputVerifier for Header support

Matthias J. Sax created KAFKA-6920: -- Summary: Enhance ConsumerRecordFactory and OutputVerifier for Header support Key: KAFKA-6920 URL: https://issues.apache.org/jira/browse/KAFKA-6920 Project: Kafka

[jira] [Reopened] (KAFKA-5697) StreamThread.shutdown() need to interrupt the stream threads to break the loop

[ https://issues.apache.org/jira/browse/KAFKA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax reopened KAFKA-5697: Assignee: (was: John Roesler) > StreamThread.shutdown() need to interrupt the stream t

Re: [VOTE] KIP-290: Support for wildcard suffixed ACLs

Hi Ron, I've incorporated both of your suggestions. Thanks Piyush Vijay On Sat, May 19, 2018 at 4:07 AM, Ron Dagostino wrote: > Hi Piyush. I think it would be better to match the flag in kafka-acls.sh > to the new enum. Instead of stating “–wildcard-suffixed-resource true” I > think “–reso

[jira] [Created] (KAFKA-6919) Trogdor documentation points to wrong location for trogdor.sh

Koen De Groote created KAFKA-6919: - Summary: Trogdor documentation points to wrong location for trogdor.sh Key: KAFKA-6919 URL: https://issues.apache.org/jira/browse/KAFKA-6919 Project: Kafka

Re: Merge order for commits to older versions?

Hello Matthias, Thanks, that makes perfect sense. I'm just used to a different system, but what you described works fine too. Now that I understand the system, I see that the PR isn't needed on 0.11.x. and can just go on trunk. Thanks for your time. On Sat, May 19, 2018 at 8:31 PM, Matthias J.

Re: Merge order for commits to older versions?

Hi, not sure if this is documented in the wiki on not (feel free to add it to the wiki :)). It works as follows: Older version branches are only used for bug fix releases and are never merged into trunk. All PRs are opened against trunk by default and if we want to get a commit into an older bran

[DISCUSS] KIP-306: Configuration for Delaying Response to Failed Client Authentication

Hi, I created a KIP that proposes we add a broker configuration to delay responses to failed client authentication. This will help prevent DoS-like situations because of a misconfigured application trying to connect with incorrect or stale credentials over and over again. Link to the KIP: https:/

Re: [DISCUSS] KIP-305: Add Connect primitive number converters

Considering this KIP is straightforward, what do you think about kicking off a vote? Or does it need more discussion time? Regards, Randall > On May 18, 2018, at 4:30 PM, Ewen Cheslack-Postava wrote: > > Yeah, the usefulness of short seems questionable, but int is probably a > large enough ran

Re: [VOTE] KIP-290: Support for wildcard suffixed ACLs

Hi Piyush. I think it would be better to match the flag in kafka-acls.sh to the new enum. Instead of stating “–wildcard-suffixed-resource true” I think “–resource-type wildcard” is much better because it allows support for new enum constants that might be added in the future via the same flag.

Merge order for commits to older versions?

Greetings, I recently created a minor PR for trunk and realized I should probably put it on 0.11.0, assuming a release of 0.11.x eventually gets merged into trunk. But looking at the GitHub branches, I found that 0.11.0 is ahead of trunk by 404 commits, which seems rather a large difference: http