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

See Changes: -- [...truncated 422815 lines...] [2022-08-18T08:37:07.281Z] [2022-08-18T08:37:07.281Z] AdjustStreamThreadCountTest > shouldResizeCacheAfterThreadRemovalTime

Re: [DISCUSS] KIP-829: (console-consumer) add print.topic property

Hi Evans, I agree "NO_TIMESTAMPTopic:topicPartition:0Offset:123 keyvalue" makes sense. Can you update the KIP in the wiki and start a vote? Thanks, Mickael On Sun, Apr 24, 2022 at 6:49 PM Chris Egerton wrote: > > Hi Evans, > > +1 for retaining the current ordering when topic p

[jira] [Created] (KAFKA-14171) mm2-offsets topic should be set retention.ms=1h or less as default

Justinwins created KAFKA-14171: -- Summary: mm2-offsets topic should be set retention.ms=1h or less as default Key: KAFKA-14171 URL: https://issues.apache.org/jira/browse/KAFKA-14171 Project: Kafka

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

See Changes: -- [...truncated 254554 lines...] [2022-08-18T11:30:04.416Z] > Task :connect:json:generateMetadataFileForMavenJavaPublication [2022-08-18T11:30:04.416Z] > Tas

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #39

See Changes: -- [...truncated 575460 lines...] [2022-08-18T11:50:20.476Z] [2022-08-18T11:50:20.476Z] org.apache.kafka.streams.integration.TableTableJoinIntegrationTest > tes

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.1 #129

See Changes: -- [...truncated 368406 lines...] [2022-08-18T12:30:09.693Z] > Task :connect:json:compileTestJava UP-TO-DATE [2022-08-18T12:30:09.693Z] > Task :connect:json:testC

Re: [VOTE] KIP-837 Allow MultiCasting a Result Record.

Hello Sophie, Thanks for your feedback. I have made all the suggested changes. One note, on how users can accomplish this in today's world , I have made up this example and have never tried myself before. But I am assuming it will work. Let me know what you think. Thanks! Sagar. On Thu, Aug 1

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

See Changes: -- [...truncated 337517 lines...] [2022-08-18T14:12:06.671Z] TableTableJoinIntegrationTest > [caching enabled = false] > org.apache.kafka.streams.integration

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

Hi Jason, Apologies for the delay in this reply. Thank you for having having a look at this KIP and sharing your suggestions. > 1. (nit): Instead of "storage id," maybe we could call it "directory id"? > It seems a little clear since each log dir gets a unique id. I agree, "directory id" is a m

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

Hi Ziming, I'm sorry it took me a while to reply. Thank you for having a look at this KIP and providing feedback. > 1. We have a version field in meta.properties, currently it’s 1, and we can > set it to 2 in this KIP, and we can give an example of server.properties and > it’s corresponding meta

Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

Hi Ismael, We can do this if we think that an external configuration is not necessary. Just wondering, is there a reason we don't want an external configuration here? Thanks, Justine On Wed, Aug 17, 2022 at 12:30 PM Ismael Juma wrote: > Why does this have to be an external config? We can provi

Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

Given that we already have `transaction.abort.timed.out.transaction.cleanup.interval.ms` and `transaction.remove.expired.transaction.cleanup.interval.ms`, it seems OK to add another one for our case here. Regarding the name, I would follow the pattern that we use for those two existing configs. We

Re: [DISCUSS] KIP-854 Separate configuration for producer ID expiry

Hi David, I chose the name to match the variable name of the existing hardcoded value. I also thought it was clearer what was happening. I'm not sure how to follow the pattern above in a way that is not overly verbose. It would have to be something like producer.id.remove.expired.producer.id.clea

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

See Changes: -- [...truncated 338372 lines...] [2022-08-18T21:21:02.536Z] > Task :connect:api:generateMetadataFileForMavenJavaPublication [2022-08-18T21:21:02.536Z] > Task

Re: [DISCUSS] KIP-844: Transactional State Stores

Hello Alex, Thanks for the replies! > As long as we allow custom user implementations of that interface, we should probably either keep that flag to distinguish between transactional and non-transactional implementations or change the contract behind the interface. What do you think? Regarding t

Re: [DISCUSS] KIP-857: Streaming recursion in Kafka Streams

Hello Nick, Thanks for the replies! They are very thoughtful. I think I agree with you that requiring the output stream to a source stream is not sufficient for a valid recursion, and even without the proposed API users today can still create a broken recursive topology. Just want to clarify anot

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

See Changes: -- [...truncated 417349 lines...] [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline]

Re: [VOTE] KIP-837 Allow MultiCasting a Result Record.

Thanks Sagar -- one thing I'm still confused about, and sorry to keep pushing on this, but the example you gave for how this works in today's world seems not to correspond to the method described in the text of the Motivation exception, ie Currently, if a user wants to replicate a message into N p