Re: [VOTE] KIP-1005: Expose EarliestLocalOffset and TieredOffset

+1 (non-binding). Thanks for the KIP! -- Kamal On Thu, Dec 21, 2023 at 2:23 PM Christo Lolov wrote: > Heya all! > > KIP-1005 ( > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1005%3A+Expose+EarliestLocalOffset+and+TieredOffset > ) > has been open for around a month with no further

Re: DISCUSS KIP-1011: Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh

Hi Ziming, Thanks for the KIP! The proposal LGTM. I'm also inclined towards option 2 (i.e. add an explicit --enable-incremental flag in 3.X version) to avoid any incompatible change in v3.X. As mentioned in this thread, many users might be using external tools to do the topic rebalance and apply

Re: [DISCUSS] KIP-1007: Introduce Remote Storage Not Ready Exception

Hi Divij, Thanks for reviewing the KIP! I've updated the KIP with the below documentation. Let me know if it needs to be changed: The consumer can read the local data as long as it knows the offset from where to fetch the data from. When there is no initial offset, the consumer decides the

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

See

[jira] [Created] (KAFKA-16049) Can you please share tutorial how to run Latest Kafka (3.6.0)

Petr Kostroun created KAFKA-16049: - Summary: Can you please share tutorial how to run Latest Kafka (3.6.0) Key: KAFKA-16049 URL: https://issues.apache.org/jira/browse/KAFKA-16049 Project: Kafka

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

See

Re: DISCUSS KIP-1011: Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh

Thank you for the summary, Ziming. Personally, I would prefer the latter i.e. having the incompatible change in 4.x instead of 3.x. This is because a major version upgrade goes through additional scrutiny by the users and usually comes with inevitable code changes required on the client. Hence,

[jira] [Resolved] (KAFKA-15619) Deleted topics will come back again

[ https://issues.apache.org/jira/browse/KAFKA-15619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Deng Ziming resolved KAFKA-15619. - Assignee: Deng Ziming Resolution: Invalid This has been fixed after setting

Re: DISCUSS KIP-1011: Use incrementalAlterConfigs when updating broker configs by kafka-configs.sh

Hello Divij Vaidya, You are right that users should update existing scripts to add ‘—disable-incremental’, and you mentioned another upgrade path which is similar, the summary of the 2 schemes are: we change existing scripts to use `incrementalAlterConfigs` and add "--disable-incremental"