[jira] [Created] (KAFKA-18754) Allow PlainSaslServer to pass client info through the negotiated properties.

Nelson B. created KAFKA-18754: - Summary: Allow PlainSaslServer to pass client info through the negotiated properties. Key: KAFKA-18754 URL: https://issues.apache.org/jira/browse/KAFKA-18754 Project: Kafka

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

Hi Chia-Ping, Sorry for the delayed response. I’ve checked all relevant JIRAs using the following Jira Query Language: project = KAFKA AND status in (Resolved, Closed) AND fixVersion = 4.0.0 AND text ~ "Remove" order by updated DESC Based on this, I checked the JIRAs related to removing deprec

Re: [DISCISS] KIP-860: Add client-provided option to guard against unintentional replication factor change during partition reassignments

Hi everyone, Thanks to Stanislav for answering the question! In the beginning I thought I’ve also updated the KIP based on the discussion above. Best, Kuan-Po On 2025/02/06 18:42:29 Chia-Ping Tsai wrote: > hi Stan > > thanks for sharing the details! > > to Kuan-Po > > Could you please tweak t

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #202

See

[jira] [Created] (KAFKA-18753) Enabling S3 Tiered Storage Causes: A fatal error has been detected by the Java Runtime Environment

Hasil Sharma created KAFKA-18753: Summary: Enabling S3 Tiered Storage Causes: A fatal error has been detected by the Java Runtime Environment Key: KAFKA-18753 URL: https://issues.apache.org/jira/browse/KAFKA-18753

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Sounds good. Thanks for clarifying. -Matthias On 2/6/25 3:19 PM, Almog Gavra wrote: Good call on the backwards compatibility - updated the KIP. Re: the grace period for BatchWindows, I think zero makes sense (and also makes implementing things a lot easier). In my mental model, we still drop

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Good call on the backwards compatibility - updated the KIP. Re: the grace period for BatchWindows, I think zero makes sense (and also makes implementing things a lot easier). In my mental model, we still drop late records that come in after the window closes, they just never happen because we use

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Hit "reply" too early. Just re-read the KIP. For `Windows#windowsFor(...)`, even if not intended to be implement by users, it's strictly public API. Thus, we cannot just change the method, but would need to keep the existing method and deprecate it, and add a new overload with a default impl t

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

BatchWindows works for me. On 2/6/25 7:34 AM, Almog Gavra wrote: Happy to name it BatchWindows. Will give some people time to chime in and then change the name. - Almog On Tue, Feb 4, 2025 at 11:10 PM Sophie Blee-Goldman wrote: One minor suggestion: use BatchWindows instead of BatchedWindo

[jira] [Created] (KAFKA-18752) Fix the warning of no-operation caused by slf4j in building kafka

Chia-Ping Tsai created KAFKA-18752: -- Summary: Fix the warning of no-operation caused by slf4j in building kafka Key: KAFKA-18752 URL: https://issues.apache.org/jira/browse/KAFKA-18752 Project: Kafka

[jira] [Resolved] (KAFKA-18275) Restarting broker in testing should use the same port

[ https://issues.apache.org/jira/browse/KAFKA-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18275. Resolution: Fixed > Restarting broker in testing should use the same port > --

Re: [DISCUSS] KIP-1124: Providing a clear Kafka Client upgrade path

hi Kuan-Po any update? Now that an upgrade path for bridge versions exists, we can introduce additional "conditions" to assist users in selecting the "best" bridge version. For example, we can provide guidance on which bridge versions offer backward compatibility with Kafka 4.0 client or are co

Re: [DISCISS] KIP-860: Add client-provided option to guard against unintentional replication factor change during partition reassignments

hi Stan thanks for sharing the details! to Kuan-Po Could you please tweak the KIP-860 according to Stan's response :) Best, Chia-Ping Stanislav Kozlovski 於 2025年2月7日 週五 上午2:32寫道： > Hey Kuan-Po! > > First of all - thanks so much for volunteering to take the implementation > of this KIP! > > W

Re: [DISCISS] KIP-860: Add client-provided option to guard against unintentional replication factor change during partition reassignments

Hey Kuan-Po! First of all - thanks so much for volunteering to take the implementation of this KIP! When I initially proposed it, I had planned with my team in Confluent to have somebody else implement it as a chance to get more experience with the open-source project. Sadly, we never got to i

[jira] [Created] (KAFKA-18751) Complete delayed FETCH request when HWM is increased.

José Armando García Sancio created KAFKA-18751: -- Summary: Complete delayed FETCH request when HWM is increased. Key: KAFKA-18751 URL: https://issues.apache.org/jira/browse/KAFKA-18751 Proj

[jira] [Resolved] (KAFKA-18750) Remove ControllerContext

[ https://issues.apache.org/jira/browse/KAFKA-18750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18750. Fix Version/s: (was: 4.1.0) Resolution: Duplicate see KAFKA-18508 > Remove Con

[jira] [Created] (KAFKA-18750) Remove ControllerContext

Chia-Ping Tsai created KAFKA-18750: -- Summary: Remove ControllerContext Key: KAFKA-18750 URL: https://issues.apache.org/jira/browse/KAFKA-18750 Project: Kafka Issue Type: Improvement

[jira] [Resolved] (KAFKA-18741) document the removal of `inter.broker.protocol.version`

[ https://issues.apache.org/jira/browse/KAFKA-18741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18741. Assignee: Nick Guo (was: Ming-Yen Chung) Resolution: Fixed trunk: https://github.c

[jira] [Resolved] (KAFKA-18483) Protect `Loggers` and `Log4jController` against `LinkageError`s

[ https://issues.apache.org/jira/browse/KAFKA-18483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18483. Fix Version/s: 4.1.0 Resolution: Fixed > Protect `Loggers` and `Log4jController` ag

[jira] [Resolved] (KAFKA-18749) remove unused fields from StateChangeLogger

[ https://issues.apache.org/jira/browse/KAFKA-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18749. Resolution: Duplicate duplicate to KAFKA-18509 > remove unused fields from StateChangeLog

[jira] [Created] (KAFKA-18749) remove unused fields from StateChangeLogger

Chia-Ping Tsai created KAFKA-18749: -- Summary: remove unused fields from StateChangeLogger Key: KAFKA-18749 URL: https://issues.apache.org/jira/browse/KAFKA-18749 Project: Kafka Issue Type: I

[jira] [Created] (KAFKA-18748) Run new integration tests separately in PRs

David Arthur created KAFKA-18748: Summary: Run new integration tests separately in PRs Key: KAFKA-18748 URL: https://issues.apache.org/jira/browse/KAFKA-18748 Project: Kafka Issue Type: Impro

Re: [DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Happy to name it BatchWindows. Will give some people time to chime in and then change the name. - Almog On Tue, Feb 4, 2025 at 11:10 PM Sophie Blee-Goldman wrote: > One minor suggestion: use BatchWindows instead of BatchedWindows. The > version without the "ed" matches up with the established n

[jira] [Resolved] (KAFKA-18618) Reduce stickiness of share session handlers

[ https://issues.apache.org/jira/browse/KAFKA-18618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18618. -- Resolution: Fixed > Reduce stickiness of share session handlers >

[jira] [Resolved] (KAFKA-18746) Remove leader.imbalance.per.broker.percentage

[ https://issues.apache.org/jira/browse/KAFKA-18746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18746. Resolution: Duplicate duplicate to KAFKA-18743 > Remove leader.imbalance.per.broker.perce

[jira] [Created] (KAFKA-18747) Persister request de-duplication

Sushant Mahajan created KAFKA-18747: --- Summary: Persister request de-duplication Key: KAFKA-18747 URL: https://issues.apache.org/jira/browse/KAFKA-18747 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-18746) Remove leader.imbalance.per.broker.percentage

黃竣陽 created KAFKA-18746: --- Summary: Remove leader.imbalance.per.broker.percentage Key: KAFKA-18746 URL: https://issues.apache.org/jira/browse/KAFKA-18746 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-18745) Handle the disconnected inter broker RPC calls within the persister

Chirag Wadhwa created KAFKA-18745: - Summary: Handle the disconnected inter broker RPC calls within the persister Key: KAFKA-18745 URL: https://issues.apache.org/jira/browse/KAFKA-18745 Project: Kafka

[jira] [Resolved] (KAFKA-18360) Remove zookeeper configurations

[ https://issues.apache.org/jira/browse/KAFKA-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18360. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/b2b24086926b0affea0bf66de

[jira] [Created] (KAFKA-18744) When I add sasl.login.callback.handler.class it is used for initial login but not used when ticket is about to expire

Anatoly created KAFKA-18744: --- Summary: When I add sasl.login.callback.handler.class it is used for initial login but not used when ticket is about to expire Key: KAFKA-18744 URL: https://issues.apache.org/jira/browse/KA

[jira] [Resolved] (KAFKA-18530) Remove ZooKeeperInternals

[ https://issues.apache.org/jira/browse/KAFKA-18530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18530. Fix Version/s: 4.0.0 Resolution: Fixed trunk: https://github.com/apache/kafka/comm

[jira] [Resolved] (KAFKA-18591) Remove QuotaConfgHandler

[ https://issues.apache.org/jira/browse/KAFKA-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18591. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/837fb1ed0250837c2d9578ce0

[jira] [Reopened] (KAFKA-18591) Remove QuotaConfgHandler

[ https://issues.apache.org/jira/browse/KAFKA-18591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened KAFKA-18591: > Remove QuotaConfgHandler > > > Key: KAFKA-18591 >

[jira] [Resolved] (KAFKA-18499) Clean up LogConfig

[ https://issues.apache.org/jira/browse/KAFKA-18499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18499. Resolution: Fixed trunk: https://github.com/apache/kafka/commit/c23d4a0d73d8ad168a0bbfcc8

[jira] [Reopened] (KAFKA-18499) Clean up LogConfig

[ https://issues.apache.org/jira/browse/KAFKA-18499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai reopened KAFKA-18499: > Clean up LogConfig > -- > > Key: KAFKA-18499 >