Build failed in Jenkins: kafka-2.4-jdk8 #132

See Changes: [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- [...truncated 5.48 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

Build failed in Jenkins: kafka-2.3-jdk8 #166

See Changes: [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- [...truncated 2.98 MB...] kafka.log.LogValidatorTest > testCompressedV1 STARTED

Build failed in Jenkins: kafka-2.2-jdk8 #22

See Changes: [github] HOTFIX: Fix broken connect transform test case due to older junit [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default --

Build failed in Jenkins: kafka-trunk-jdk11 #1108

See Changes: [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- [...truncated 5.77 MB...]

Build failed in Jenkins: kafka-2.0-jdk8 #310

See Changes: [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- [...truncated 437.45 KB...] kafka.log.LogCleanerTest >

Build failed in Jenkins: kafka-2.1-jdk8 #251

See Changes: [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- [...truncated 467.27 KB...] kafka.log.LogValidatorTest >

[jira] [Created] (KAFKA-9475) Replace transaction abortion scheduler with a delayed queue

Boyang Chen created KAFKA-9475: -- Summary: Replace transaction abortion scheduler with a delayed queue Key: KAFKA-9475 URL: https://issues.apache.org/jira/browse/KAFKA-9475 Project: Kafka Issue

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Thank you Matthias for the use cases! Looking at both use cases, I think you need to elaborate on them in the KIP, Richard. Emit from plain KTable: I agree with Matthias that the lower timestamp makes sense because it marks the start of the validity of the record. Idempotent records with a

Build failed in Jenkins: kafka-2.2-jdk8-old #203

See Changes: [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node

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

See Changes: [rajinisivaram] MINOR: MiniKdc JVM shutdown hook fix (#7946) [jason] KAFKA-9254; Overridden topic configs are reset after dynamic default -- [...truncated

[jira] [Resolved] (KAFKA-9254) Updating Kafka Broker configuration dynamically twice reverts log configuration to default

[ https://issues.apache.org/jira/browse/KAFKA-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9254. Fix Version/s: 2.4.1 2.3.2 2.2.3

Re: [DISCUSS] KIP-546: Add quota-specific APIs to the Admin Client, redux

Thanks for reviewing, Anna, In the describe call, the idea is that the API will match the QuotaFilters, which can be specified in two ways for your example (filter is a type and a matching string): 1) (USER="user-1") returns both 2) (USER="user-1", CLIENT_ID="") returns just

Build failed in Jenkins: kafka-2.2-jdk8-old #202

See Changes: [github] HOTFIX: Fix broken connect transform test case due to older junit -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node

Build failed in Jenkins: kafka-trunk-jdk11 #1107

See Changes: [bbejeck] KAFKA-9152; Improve Sensor Retrieval (#7928) [rajinisivaram] MINOR: MiniKdc JVM shutdown hook fix (#7946) -- [...truncated 2.85 MB...]

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

See Changes: [bbejeck] KAFKA-9152; Improve Sensor Retrieval (#7928) -- [...truncated 2.83 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: [DISCUSS] KIP-546: Add quota-specific APIs to the Admin Client, redux

Hi Brian, The KIP looks good! I have one clarification question regarding the distinction between describe and resolve API. Suppose I set request quota for /config/users/”user-1”/clients/"client-1" to 100 and request quota for /config/users/”user-1” to 200. Is this correct that

Build failed in Jenkins: kafka-trunk-jdk11 #1106

See Changes: [bbejeck] KAFKA-7317: Use collections subscription for main consumer to reduce [rhauch] Correct exception message in DistributedHerder (#7995) --

Re: [VOTE] KIP-515: Hardened TLS Configs to ZooKeeper

Hi everyone. This concludes the vote for KIP 515. The vote passes with +1 binding votes from Gwen, Rajini, and Manikumar and a +1 non-binding vote from Mitch. I have marked the KIP as "Accepted" and opened a pull request at https://github.com/apache/kafka/pull/8003. Ron Ron On Thu, Jan 23,

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

See Changes: [bbejeck] KAFKA-7317: Use collections subscription for main consumer to reduce [rhauch] Correct exception message in DistributedHerder (#7995) --

[jira] [Resolved] (KAFKA-9152) Improve Sensor Retrieval

[ https://issues.apache.org/jira/browse/KAFKA-9152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-9152. Resolution: Fixed > Improve Sensor Retrieval > - > > Key:

Re: [VOTE] KIP-559: Make the Kafka Protocol Friendlier with L7 Proxies

Hi all, The vote has passed with +5 binding votes (Jason Gustafson, David Arthur, Gwen Shapira, Guozhang Wang, Harsha Chintalapani) and +2 non-binding votes (Eno Thereska, Satish Duggana). Thanks to everyone! Best, David On Thu, Jan 23, 2020 at 10:46 PM Satish Duggana wrote: > +1

[jira] [Created] (KAFKA-9474) Kafka RPC protocol should support type 'double'

Brian Byrne created KAFKA-9474: -- Summary: Kafka RPC protocol should support type 'double' Key: KAFKA-9474 URL: https://issues.apache.org/jira/browse/KAFKA-9474 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-9462) Correct exception message in DistributedHerder

[ https://issues.apache.org/jira/browse/KAFKA-9462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-9462. -- Reviewer: Randall Hauch Resolution: Fixed Thanks, [~yuzhih...@gmail.com]. Merged to the

[jira] [Created] (KAFKA-9473) A large number of core system tests failing due to Kafka server failed to start on trunk

Boyang Chen created KAFKA-9473: -- Summary: A large number of core system tests failing due to Kafka server failed to start on trunk Key: KAFKA-9473 URL: https://issues.apache.org/jira/browse/KAFKA-9473

[jira] [Resolved] (KAFKA-7317) Use collections subscription for main consumer to reduce metadata

[ https://issues.apache.org/jira/browse/KAFKA-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-7317. Resolution: Fixed > Use collections subscription for main consumer to reduce metadata >

Re: [DISCUSS] KIP-546: Add quota-specific APIs to the Admin Client, redux

My apologies, Rajini. My hasty edits omitted a couple spots. I've done a more thorough scan and should have cleaned up (1) and (2). For (3), Longs are chosen because that's what the ConfigCommand currently uses, and because there's no floating point type in the RPC protocol. Longs didn't seem to

[jira] [Resolved] (KAFKA-8821) Avoid pattern subscription to allow for stricter ACL settings

[ https://issues.apache.org/jira/browse/KAFKA-8821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-8821. Resolution: Fixed Resolved via [https://github.com/apache/kafka/pull/7969] > Avoid pattern

Re: [DISCUSS] KIP-546: Add quota-specific APIs to the Admin Client, redux

Thanks Brian. Looks good. Just a few minor points: 1) We can remove *public ResolveClientQuotasOptions setOmitOverriddenValues(boolean omitOverriddenValues); * 2) Under ClientQuotasCommand, the three items are List/Describe/Alter, rename to match the new naming for operations? 3) Request quota

Re: [KAFKA-557] Add emit on change support for Kafka Streams

IMHO, the question about semantics depends on the use case, in particular on the origin of a KTable. If there is a changlog topic that one reads directly into a KTable, emit-on-change does actually make sense, because the timestamp indicates _when_ the update was _effective_. For this case, it is

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Hi Bruno, Thanks for that idea. I hadn't considered that option before, and it does seem like that would be the right place to put it if we think it might be semantically important to control on a table-by-table basis. I had been thinking of it less semantically and more practically. In the

Re: [DISCUSS] KIP-546: Add quota-specific APIs to the Admin Client, redux

Thanks again, Rajini, Units will have to be implemented on a per-config basis, then. I've removed all language reference to units and replaced QuotaKey -> String (config name). I've also renamed DescribeEffective -> Resolve, and replaced --list with --describe, and --describe to --resolve to be

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Hi Richard, Thank you for the KIP. I agree with John that we should focus on the interface and behavior change in a KIP. We can discuss the implementation later. I am also +1 for the survey. I had a thought about this. Couldn't we consider emit-on-change to be one config of suppress (like

Re: [KAFKA-557] Add emit on change support for Kafka Streams

Hi Richard, Thanks for picking this up! I know of at least one large community member for which this feature is absolutely essential. If I understand your two options, it seems like the proposal is to implement it as a behavior change regardless, and the question is whether to provide an

[jira] [Resolved] (KAFKA-9471) Throw exception for DEAD StreamThread.State

[ https://issues.apache.org/jira/browse/KAFKA-9471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Yu resolved KAFKA-9471. --- Resolution: Duplicate > Throw exception for DEAD StreamThread.State >

Re: [DISCUSS] KIP-567: Kafka Cluster Audit

Hello Igor, Thanks for your KIP  It would be great to adopt this functionality and getting the best of tracking cluster activity. +1 vote from me Cheers, Alex Dunayevsky On Fri, 24 Jan 2020, 15:35 Игорь Мартемьянов, wrote: > Motivation: > > > *It is highly demanded in most businesses to

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

See Changes: [github] KAFKA-9181; Maintain clean separation between local and group -- [...truncated 5.73 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: KIP-560 Discuss

Hi all, thanks for the explanation. I was also not sure how the kip would be possible to implement. No that it does seem plausible, my only feedback is that the command line option could align better with the existing one. That is, the existing option is called “—input-topics”, so it seems

Build failed in Jenkins: kafka-trunk-jdk11 #1105

See Changes: [github] KAFKA-9181; Maintain clean separation between local and group -- [...truncated 2.85 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: [DISCUSS] KIP-567: Kafka Cluster Audit

Motivation: *It is highly demanded in most businesses to have the ability of obtaining audit information in case someone changes cluster configuration (like creation/deletion/modify/description of any topic or ACLs).We may add this ability. Since audit requirements are so broad, it's impractical

[DISCUSS] KIP-567: Kafka Cluster Audit

Hello there. Please review this KIP. Thanks.

[jira] [Resolved] (KAFKA-9181) Flaky test kafka.api.SaslGssapiSslEndToEndAuthorizationTest.testNoConsumeWithoutDescribeAclViaSubscribe

[ https://issues.apache.org/jira/browse/KAFKA-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajini Sivaram resolved KAFKA-9181. --- Fix Version/s: 2.5.0 Reviewer: Jason Gustafson Resolution: Fixed > Flaky

Re: [DISCUSS] KIP-546: Add quota-specific APIs to the Admin Client, redux

Hi Brian, Thanks for the responses. 4) Yes, agree that it would be simpler to leave units out of the initial design. We currently have units that are interpreted by the configurable callback. The default callback interprets the value as per-broker-bytes-per-second and