Re: Confluence permission for KIP

Hi, Seems the Confluence account has not been created at that time. Could you help to check again? Johnny Wang 於 2025年3月6日 週四 上午1:56寫道： > Hi, > > I am new to Apache Kafka. Could someone give me permission of Kafka > Confluence ( > > https://cwiki.apache.org/confluence/display/kafka ) for writin

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.8 #150

See

[jira] [Created] (KAFKA-18933) Extract an interface from ClusterInstance for Java 11 modules

David Arthur created KAFKA-18933: Summary: Extract an interface from ClusterInstance for Java 11 modules Key: KAFKA-18933 URL: https://issues.apache.org/jira/browse/KAFKA-18933 Project: Kafka

[jira] [Created] (KAFKA-18937) Consider to add kraft state to BootstrapMetadata

PoAn Yang created KAFKA-18937: - Summary: Consider to add kraft state to BootstrapMetadata Key: KAFKA-18937 URL: https://issues.apache.org/jira/browse/KAFKA-18937 Project: Kafka Issue Type: Improv

[jira] [Resolved] (KAFKA-18918) Share partition lock held for onComplete exception

[ https://issues.apache.org/jira/browse/KAFKA-18918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-18918. --- Fix Version/s: 4.1.0 Resolution: Fixed > Share partition lock held for onComplete exc

[jira] [Resolved] (KAFKA-18811) Allow passing the Consumer Configs to the AdminClientProperties for VerifiableShareConsumers

[ https://issues.apache.org/jira/browse/KAFKA-18811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18811. -- Fix Version/s: 4.1.0 Resolution: Fixed > Allow passing the Consumer Configs to

[jira] [Created] (KAFKA-18936) Share fetch stuck when records are larger than fetch max bytes

Apoorv Mittal created KAFKA-18936: - Summary: Share fetch stuck when records are larger than fetch max bytes Key: KAFKA-18936 URL: https://issues.apache.org/jira/browse/KAFKA-18936 Project: Kafka

[jira] [Created] (KAFKA-18934) Consider making records in FetchResponse not nullable

Ismael Juma created KAFKA-18934: --- Summary: Consider making records in FetchResponse not nullable Key: KAFKA-18934 URL: https://issues.apache.org/jira/browse/KAFKA-18934 Project: Kafka Issue Typ

Re: Protected Branches and Required Checks

Thanks David. I think you're saying that the second check only applies to PRs and not to direct pushes to trunk. If so, I understand now. Ismael On Thu, Mar 6, 2025 at 9:26 AM David Arthur wrote: > Sorry, let me clarify that point. > > There are two proposed rulesets (full details in the INFRA

Re: [VOTE] 4.0.0 RC1

Hi, David, We merged https://github.com/apache/kafka/pull/19131 to 4.0. So this issue is resolved. Thanks, Jun On Wed, Mar 5, 2025 at 11:08 PM David Jacot wrote: > Hi Jun, > > Thanks for letting me know. I agree that this is nothing that we need to > sort out before 4.0 goes out. I suggest yo

Re: [DISCUSS] KIP-896: Remove old client protocol API versions in Kafka 4.0

Hi, Ismael, Thanks for the reply. Yes, that's the main issue. By changing a field to non-nullable without a version bump, it implies that this change applies to all existing versions. If anyone implements this protocol for a client, the client could break when talking to a broker before 4.0. Sin

Re: Protected Branches and Required Checks

Hi David, I don't follow the following: * Require all changes to trunk to flow through a PR That's exactly the case Chia-Ping was asking about that you said is _not_ expected. Ismael On Thu, Mar 6, 2025 at 8:01 AM David Arthur wrote: > Indeed, what I was trying to achieve is not possible w

Re: Protected Branches and Required Checks

hi David It appears we can't push reverted commits to trunk from our local repository. See the following error message. remote: Resolving deltas: 100% (15/15), completed with 11 local objects. remote: error: GH006: Protected branch update failed for refs/heads/trunk. remote: remote: - Changes m

Re: Protected Branches and Required Checks

Indeed, what I was trying to achieve is not possible with the legacy branch protections that are configured via asf.yaml. I have reverted that change. I filed https://issues.apache.org/jira/browse/INFRA-26603 which should let us accomplish the following: * Protect trunk and release branches from

[jira] [Created] (KAFKA-18932) Remove partitionMaxBytes usage from brokers for share fetch requests

Abhinav Dixit created KAFKA-18932: - Summary: Remove partitionMaxBytes usage from brokers for share fetch requests Key: KAFKA-18932 URL: https://issues.apache.org/jira/browse/KAFKA-18932 Project: Kafka

[jira] [Created] (KAFKA-18931) Debug the case where kafka-share-groups.sh --describe --members does not match with the reality when share consumer is closed during broker outage

Chirag Wadhwa created KAFKA-18931: - Summary: Debug the case where kafka-share-groups.sh --describe --members does not match with the reality when share consumer is closed during broker outage Key: KAFKA-18931 URL

[jira] [Created] (KAFKA-18930) KRaft MigrationEvent won't retry when failing to write data to ZK

Luke Chen created KAFKA-18930: - Summary: KRaft MigrationEvent won't retry when failing to write data to ZK Key: KAFKA-18930 URL: https://issues.apache.org/jira/browse/KAFKA-18930 Project: Kafka

Re: Protected Branches and Required Checks

Hm, this wasn't my intention with this change. I was expected two things to change: 1) PRs could only be merged if a required check passed 2) Forced pushes were disabled I was not expecting regular push to be disabled since there is a separate config for that (Screenshot from a different repo) [

[jira] [Resolved] (KAFKA-18246) Fix ConnectRestApiTest.test_rest_api by adding multiversioning configs

[ https://issues.apache.org/jira/browse/KAFKA-18246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-18246. Fix Version/s: 4.1.0 (was: 4.0.0) Resolution: Fixed > Fix Co

[jira] [Created] (KAFKA-18929) Log a warning when a time retention based segment has a future timestamp

Daniel Urban created KAFKA-18929: Summary: Log a warning when a time retention based segment has a future timestamp Key: KAFKA-18929 URL: https://issues.apache.org/jira/browse/KAFKA-18929 Project: Kaf

Re: KIP-1135: Deprecated "org.apache.kafka.disallowed.login.modules"

Thanks for your review. Would it be better to change the title to “Modify JAAS” logic? Chia-Ping Tsai 于2025年3月6日周四 16:32写道： > hi Xuan-Zhang > > Thanks for this kip. Please take a look at following questions. > > cp00: > the description "(optional) we can deprecate > `org.apache.kafka.disallowed.