[jira] [Resolved] (KAFKA-15131) Improve RemoteStorageManager exception handling documentation

[ https://issues.apache.org/jira/browse/KAFKA-15131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-15131. -- Resolution: Fixed > Improve RemoteStorageManager exception han

Re: [DISCUSS] KIP-793: Sink Connectors: Support topic-mutating SMTs for async connectors (preCommit users)

Hi Chris, Thanks for pointing that out, I hadn't realized that the SubmittedRecords class has almost exactly the same semantics needed for handling offset commits in the per-sink record ack API case. However, I agree that it isn't worth the tradeoff and we've already discussed the backward compati

[VOTE] KIP-793: Allow sink connectors to be used with topic-mutating SMTs

Hi all, I'd like to start a vote on KIP-793 which enables sink connector implementations to be used with SMTs that mutate the topic / partition / offset information of a record. KIP - https://cwiki.apache.org/confluence/display/KAFKA/KIP-793%3A+Allow+sink+connectors+to+be+used+with+topic-mutating

[DISCUSS] Release plan for Apache Kafka 3.5.1 release

Hi folks Here's the release plan for https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.5.1 3.5.1 will be a bug fix release which also addresses some of the CVEs such as CVE-2023-34455 [1] in snappy-java. If all goes smoothly, I am estimating a release date in the 3rd or 4th week of

Re: [DISCUSS] Release plan for Apache Kafka 3.5.1 release

Hi Divij, Thanks for sharing the 3.5.1 release plan. The "Open/Blocked/Merged Issues" sections in the wiki seem to point to 3.4.1 release instead of 3.5.1 release. ~Satish. On Mon, 3 Jul 2023 at 17:22, Divij Vaidya wrote: > > Hi folks > > Here's the release plan for > https://cwiki.apache.org/c

Re: [DISCUSS] Release plan for Apache Kafka 3.5.1 release

Hi Divij, Thanks for the release plan. I wonder if we should wait a little more as 3.5.0 was released on June 15th. Releasing 3.5.1 a month after seems not enough in order to have time to catch bugs in 3.5.0. I think that we usually release the first minor release ~3 months after the major one. I

Re: [DISCUSS] KIP-852 Optimize calculation of size for log in remote tier

Thanks Divij for taking the feedback and updating the motivation section in the KIP. One more comment on Alternative solution-3, The con is not valid as that will not affect the broker restart times as discussed in the earlier email in this thread. You may want to update that. ~Satish. On Sun, 2

[jira] [Created] (KAFKA-15142) Add Client Metadata to RemoteStorageFetchInfo

Jorge Esteban Quilcate Otoya created KAFKA-15142: Summary: Add Client Metadata to RemoteStorageFetchInfo Key: KAFKA-15142 URL: https://issues.apache.org/jira/browse/KAFKA-15142 Project:

Re: [DISCUSS] Release plan for Apache Kafka 3.5.1 release

Satish - Thank you for catching that. It is now fixed. David - Please refer to the security@kafka mailing thread with "Reg CVE 2023-34455" where it was proposed to have an early release for 3.5.1. The rationale of releasing 3.5.1 early is to have a version of Kafka released which does not have any

Re:[DISCUSS] KIP-943: Add independent "offset.storage.segment.bytes" for connect-distributed.properties

Is anyone following this KIP? Bump this thread.

Re: Subscribe to Kafka dev mailing list

Hello You sent this email to the wrong email address. Please find instruction on how to subscribe at https://kafka.apache.org/contact -- Divij Vaidya On Sun, Jul 2, 2023 at 10:59 PM 最红 <1559063...@qq.com.invalid> wrote: > Subscribe to Kafka dev mailing list

Re: [VOTE] KIP-793: Allow sink connectors to be used with topic-mutating SMTs

Hi Yash, Thanks for the KIP! +1 (binding) Cheers, Chris On Mon, Jul 3, 2023 at 7:02 AM Yash Mayya wrote: > Hi all, > > I'd like to start a vote on KIP-793 which enables sink connector > implementations to be used with SMTs that mutate the topic / partition / > offset information of a record.

Re: [DISCUSS] KIP-892: Transactional Semantics for StateStores

Hi Nick, Thanks for the insights! Very interesting! As far as I understand, you want to atomically update the state store from the transaction buffer, flush the memtable of a state store and write the checkpoint not after the commit time elapsed but after the transaction buffer reached a size

[jira] [Created] (KAFKA-15143) FixedKeyMockProcessorContext is missing from test-utils

Tomasz Kaszuba created KAFKA-15143: -- Summary: FixedKeyMockProcessorContext is missing from test-utils Key: KAFKA-15143 URL: https://issues.apache.org/jira/browse/KAFKA-15143 Project: Kafka I

[GitHub] [kafka-site] divijvaidya merged pull request #529: Update coding-guide.html

divijvaidya merged PR #529: URL: https://github.com/apache/kafka-site/pull/529 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apa

[GitHub] [kafka-site] divijvaidya commented on pull request #529: Update coding-guide.html

divijvaidya commented on PR #529: URL: https://github.com/apache/kafka-site/pull/529#issuecomment-1618574725 Thank you for fixing this typo @imranhirey! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to

[GitHub] [kafka-site] mimaison commented on pull request #529: Update coding-guide.html

mimaison commented on PR #529: URL: https://github.com/apache/kafka-site/pull/529#issuecomment-1618628168 Am I missing something? This is not fixing a typo, this is introducing one! It's replacing `them` with `themnn` -- This is an automated message from the Apache Git Service. To respond

Re: [DISCUSS] KIP-892: Transactional Semantics for StateStores

Hi Bruno Yes, that's correct, although the impact on IQ is not something I had considered. What about atomically updating the state store from the transaction > buffer every commit interval and writing the checkpoint (thus, flushing > the memtable) every configured amount of data and/or number of

[GitHub] [kafka-site] divijvaidya commented on pull request #529: Update coding-guide.html

divijvaidya commented on PR #529: URL: https://github.com/apache/kafka-site/pull/529#issuecomment-1618645568 > Am I missing something? This is not fixing a typo, this is introducing one! It's replacing them with themnn Ah no! You are right. It's me being hasty and confusing the change

[GitHub] [kafka-site] divijvaidya opened a new pull request, #530: Revert "MINOR: Fix typo in coding-guide.html (#529)"

divijvaidya opened a new pull request, #530: URL: https://github.com/apache/kafka-site/pull/530 This reverts commit 4de394f2ff19eef742b9e08098e329da2c7d0146. I, incorrect merged a PR introducing a typo! Reverting that change. -- This is an automated message from the Apache Git Servi

[jira] [Created] (KAFKA-15144) Checkpoint downstreamOffset stuck to 1

Edoardo Comar created KAFKA-15144: - Summary: Checkpoint downstreamOffset stuck to 1 Key: KAFKA-15144 URL: https://issues.apache.org/jira/browse/KAFKA-15144 Project: Kafka Issue Type: Bug

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

See

[GitHub] [kafka-site] divijvaidya merged pull request #530: Revert "MINOR: Fix typo in coding-guide.html (#529)"

divijvaidya merged PR #530: URL: https://github.com/apache/kafka-site/pull/530 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@kafka.apa

Re: [VOTE] KIP-793: Allow sink connectors to be used with topic-mutating SMTs

Hey Yash, Thanks so much for your effort in the design and discussion phase! +1 (non-binding) Greg On Mon, Jul 3, 2023 at 7:19 AM Chris Egerton wrote: > > Hi Yash, > > Thanks for the KIP! +1 (binding) > > Cheers, > > Chris > > On Mon, Jul 3, 2023 at 7:02 AM Yash Mayya wrote: > > > Hi all, > >

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

See

Re: [DISCUSS] KIP-942: Add Power(ppc64le) support

I agree with Divij. A nightly Apache Kafka build for PowerPC would be welcome. But it shouldn't run on every build, since the extra time and complexity would not be worth it. By the way, are there any features or plugins we don't intend to support on PPC? If there are, this KIP would be a good

Re: [VOTE] KIP-858: Handle JBOD broker disk failure in KRaft

On Mon, Jun 26, 2023, at 05:08, Igor Soarez wrote: > Hi Colin, > > Thanks for your support with getting this over the line and that’s > great re the preliminary pass! Thanks also for sharing your > thoughts, I've had a careful look at each of these and sharing my > comments below. > > I agree, it i