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

2023-06-27 Thread Apache Jenkins Server
See

Re: [VOTE] KIP-937: Improve Message Timestamp Validation

2023-06-27 Thread Beyene, Mehari
Hi all, I would like thank you all of you for participating in the voting process. After being open for 11 days, we have received the necessary votes to proceed, and I am now closing the voting process. KIP-937 has been accepted with 3 binding votes from Luke Chen, Divij Vaidya, and Justine Ols

Re: [VOTE] KIP-937: Improve Message Timestamp Validation

2023-06-27 Thread Justine Olshan
Hey Mehari, Yes. The KIP looks good to me. +1 (binding) Justine On Tue, Jun 27, 2023 at 12:13 PM Beyene, Mehari wrote: > Hi Justine/All, > > I want to wrap up this voting process in the next day or so. Justine, > since you gave a conditional binding vote regarding updating the error > message,

Re: [VOTE] KIP-937: Improve Message Timestamp Validation

2023-06-27 Thread Beyene, Mehari
Hi Justine/All, I want to wrap up this voting process in the next day or so. Justine, since you gave a conditional binding vote regarding updating the error message, I want to circle back and verify that you're happy with the current state of the changes before concluding the voting process. T

Re: [DISCUSS] KIP-937 Improve Message Timestamp Validation

2023-06-27 Thread Beyene, Mehari
Hi Gaurav, You have a valid concern regarding the proposed default value for log.message.timestamp.after.max.ms being only 1 hour. We can keep this as Long.MAX_VALUE for the first phase implementation of this KIP and change the default value to 1 hour in future iterations. In the meantime, us

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #1953

2023-06-27 Thread Apache Jenkins Server
See Changes: -- [...truncated 580539 lines...] [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // timestamp

Re: [VOTE] KIP-937: Improve Message Timestamp Validation

2023-06-27 Thread Christo Lolov
+1 (non-binding) from me as well! This is the type of problem which is difficult to become aware of so the more guardrails we put into place the better. On Wed, 21 Jun 2023 at 23:30, Beyene, Mehari wrote: > Thank you, Justin. That makes sense. > I have updated the KIP to remove the concept of ah

[GitHub] [kafka-site] mimaison commented on pull request #528: MINOR: Add statmenet about ZK deprecation to 3.5 release blog post

2023-06-27 Thread via GitHub
mimaison commented on PR #528: URL: https://github.com/apache/kafka-site/pull/528#issuecomment-1609796788 Yes, that plan looks good to me. -- 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 spe

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

2023-06-27 Thread hudeqi
Hi, all. I want to submit a minor kip, and hope get some review and good suggestions. the kip is here: https://cwiki.apache.org/confluence/x/vhw0Dw Motivation: As the config 'segment.bytes' for internal topic related connect cluster(offset.storage.topic), if following the default configuration

Re: [DISCUSS] KIP-940: Broker extension point for validating record contents at produce time

2023-06-27 Thread Edoardo Comar
Hi Jorge thanks for the feedback. Comments inline below > 1. Similar to Kirk's first point, I'm also concerned on how would the > plugin developers / operators be able to apply multiple policies and how > configurations would be passed to each policy. We’ve only attempted to tackle the “one plugi

Fwd: Offsets: consumption and production in rollback

2023-06-27 Thread Andrew Schofield
Hi Henry, Thanks for your message. Kafka transactions are a bit unusual. If you produce a message inside a transaction, it is assigned an offset on a topic-partition before the transaction even commits. That offset is not “revoked” if the transaction rolls back. This is why the consumer has the

Re: How to Integrate MySQL database with Kafka? Need Demo

2023-06-27 Thread Avani Panchal
thanks Roman. On Tue, Jun 27, 2023 at 3:15 PM Roman Schmitz wrote: > Hi Avani, > > not sure what you mean by creating your own code. Of course you can write > an own Connector but especially in Source Connectors offset handling can > challenging depending on the system. > There are hundreds of d

Offsets: consumption and production in rollback

2023-06-27 Thread Henry GALVEZ
I have some doubts regarding message consumption and production, as well as transactional capabilities. I am using a Kafka template to produce a message within a transaction. After that, I execute another transaction that produces a message and intentionally throws a runtime exception to simulat

Re: How to Integrate MySQL database with Kafka? Need Demo

2023-06-27 Thread Roman Schmitz
Hi Avani, not sure what you mean by creating your own code. Of course you can write an own Connector but especially in Source Connectors offset handling can challenging depending on the system. There are hundreds of different Connectors out there that can connect to existing systems. If you find o

Re: How to Integrate MySQL database with Kafka? Need Demo

2023-06-27 Thread Avani Panchal
Hi Roman, Thanks for replying, I want to ask one question: can I create my own code to integrate data using Kafka connectors? Kind regards, Avani Panchal On Tue, Jun 27, 2023 at 12:29 PM Roman Schmitz wrote: > Hi Avani, > > totally agree - depending on the way you'd like to integrate your sour

[jira] [Created] (KAFKA-15128) snappy-java-1.1.8.4.jar library vulnerability

2023-06-27 Thread priyatama (Jira)
priyatama created KAFKA-15128: - Summary: snappy-java-1.1.8.4.jar library vulnerability Key: KAFKA-15128 URL: https://issues.apache.org/jira/browse/KAFKA-15128 Project: Kafka Issue Type: Bug