[jira] [Resolved] (KAFKA-16357) Kafka Client JAR manifest breaks javac linting

[ https://issues.apache.org/jira/browse/KAFKA-16357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-16357. - Resolution: Duplicate > Kafka Client JAR manifest breaks javac linting >

Re: [DISCUSS] KIP-1027 Add MockFixedKeyProcessorContext

Thanks for the KIP Shashwat. Closing this testing gap is great! It did come up a few time already... One question: why do you propose to `extend MockProcessorContext`? Given how the actual runtime context classes are setup, it seems that the regular context and fixed-key-context are distinct,

Re: [DISCUSS] KIP-1020: Deprecate `window.size.ms` in `StreamsConfig`

Yes, it's used inside `TimeWindowedSerializer` and actually also inside `TimeWindowDeserializer`. However, it does IMHO not change that we should remove it from `StreamsConfig` because both configs are not intended to be used in Java code... If one writes Java code, they should use new

[jira] [Resolved] (KAFKA-16360) Release plan of 3.x kafka releases.

[ https://issues.apache.org/jira/browse/KAFKA-16360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-16360. - Resolution: Invalid Please don't use Jira to ask questions. Jira tickets are for bug

[DISCUSS] KIP-1027 Add MockFixedKeyProcessorContext

Hi everyone, I would like to start the discussion on https://cwiki.apache.org/confluence/display/KAFKA/KIP-1027%3A+Add+MockFixedKeyProcessorContext This adds MockFixedKeyProcessorContext to the Kafka Streams Test Utils library. Regards, Shashwat Pandey

[jira] [Created] (KAFKA-16366) Refactor KTable source optimization

Matthias J. Sax created KAFKA-16366: --- Summary: Refactor KTable source optimization Key: KAFKA-16366 URL: https://issues.apache.org/jira/browse/KAFKA-16366 Project: Kafka Issue Type:

[jira] [Created] (KAFKA-16365) AssignmentsManager mismanages completion notifications

Igor Soarez created KAFKA-16365: --- Summary: AssignmentsManager mismanages completion notifications Key: KAFKA-16365 URL: https://issues.apache.org/jira/browse/KAFKA-16365 Project: Kafka Issue

[jira] [Created] (KAFKA-16364) MM2 High-Resolution Offset Translation

Greg Harris created KAFKA-16364: --- Summary: MM2 High-Resolution Offset Translation Key: KAFKA-16364 URL: https://issues.apache.org/jira/browse/KAFKA-16364 Project: Kafka Issue Type: New Feature

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.7 #108

See Changes: -- [...truncated 457202 lines...] [2024-03-11T21:23:32.885Z] > Task :group-coordinator:testClasses [2024-03-11T21:23:33.983Z] > Task :core:compileScala

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.6 #149

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #2715

See

[jira] [Created] (KAFKA-16363) Storage crashes if dir is unavailable

Igor Soarez created KAFKA-16363: --- Summary: Storage crashes if dir is unavailable Key: KAFKA-16363 URL: https://issues.apache.org/jira/browse/KAFKA-16363 Project: Kafka Issue Type: Sub-task

Re: [DISCUSS] KIP-1020: Deprecate `window.size.ms` in `StreamsConfig`

PS-- I was re-reading the PR that originated this discussion and realized that `window.inner.serde.class` is used here in KStreams. This goes against removing it,

Re: [DISCUSS] KIP-1020: Deprecate `window.size.ms` in `StreamsConfig`

Sophie, I'll add a paragraph about removing `windowed.inner.serde.class` to the KIP. I'll also add putting it in the `TimeWindowedSerde` class with some add'tl guidance on the docs addition. Also, I double-checked setting window.size.ms on the client and it doesn't throw an error at all, in

Re: [DISCUSS] KIP-853: KRaft Controller Membership Changes

Hi Jun Thanks for the feedback. See my comments below. On Wed, Mar 6, 2024 at 4:47 PM Jun Rao wrote: > 20.1. It seems that the PreferredSuccessors field didn't get fixed. It's > still there together with PreferredCandidates. > +{ "name": "PreferredSuccessors", "type": "[]int32",

[DISCUSS] Minimum constraint for segment.ms

Hey folks Before I file a KIP to change this in 4.0, I wanted to understand the historical context for the value of the following setting. Currently, segment.ms minimum threshold is set to 1ms [1]. Segments are expensive. Every segment uses multiple file descriptors and it's easy to run out of

[jira] [Created] (KAFKA-16362) Fix type-unsafety in KStreamKStreamJoin caused by isLeftSide

Greg Harris created KAFKA-16362: --- Summary: Fix type-unsafety in KStreamKStreamJoin caused by isLeftSide Key: KAFKA-16362 URL: https://issues.apache.org/jira/browse/KAFKA-16362 Project: Kafka

[jira] [Created] (KAFKA-16361) Rack aware sticky assignor minQuota violations

Luke D created KAFKA-16361: -- Summary: Rack aware sticky assignor minQuota violations Key: KAFKA-16361 URL: https://issues.apache.org/jira/browse/KAFKA-16361 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-16360) Release plan of 3.x kafka releases.

kaushik srinivas created KAFKA-16360: Summary: Release plan of 3.x kafka releases. Key: KAFKA-16360 URL: https://issues.apache.org/jira/browse/KAFKA-16360 Project: Kafka Issue Type:

Re: [VOTE] KIP-995: Allow users to specify initial offsets while creating connectors

Thanks Folks, Renamed the field to `offsets_status`. And now that we have 3 binding votes, I will update the KIP status to `accepted` . Thanks again for all the valuable feedback. Ashwin On Wed, Mar 6, 2024 at 2:42 PM Chris Egerton wrote: > Hi Yash, > > Thanks for the follow-up, I like the

Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #2714

See

[jira] [Created] (KAFKA-16359) kafka-clients-3.7.0.jar published to Maven Central is defective

Jeremy Norris created KAFKA-16359: - Summary: kafka-clients-3.7.0.jar published to Maven Central is defective Key: KAFKA-16359 URL: https://issues.apache.org/jira/browse/KAFKA-16359 Project: Kafka

Re: [DISCUSS] KIP-956: Tiered Storage Quotas

Hi Abhijeet, Thanks for the KIP! Looks good to me. I just have a minor comments on naming: Would it be work to align the config names to existing quota names? e.g. `remote.log.manager.copy.byte.rate.quota` (or similar) instead of `remote.log.manager.copy.max.bytes.per.second`? Same for new

Re: [DISCUSS] KIP-1026: Handling producer snapshot when upgrading from < v2.8.0 for Tiered Storage

Hi All, Just a Reminder, KIP-1026 is open for discussion. Thanks and Regards Arpit Goyal 8861094754 On Sat, Mar 9, 2024 at 9:27 AM Arpit Goyal wrote: > Hi All, > > I have created KIP-1026 for handling producerSnapshot empty scenarios > when the topic is upgraded from the kafka < 2.8 version.

[jira] [Reopened] (KAFKA-10199) Separate state restoration into separate threads

[ https://issues.apache.org/jira/browse/KAFKA-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna reopened KAFKA-10199: --- > Separate state restoration into separate threads >