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

See

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.3 #114

See

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

See

Re: Streams: clarification needed, checkpoint vs. position files

Hi all, Just to clarify: there actually is a position file. It was a small detail of the IQv2 implementation to add it, otherwise a persistent store's position would be lost after a restart. Otherwise, Sophie is right on the money. The checkpoint refers to an offset in the changelog, while

[jira] [Created] (KAFKA-14385) Flaky Test QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAvailable

A. Sophie Blee-Goldman created KAFKA-14385: -- Summary: Flaky Test QueryableStateIntegrationTest.shouldNotMakeStoreAvailableUntilAllStoresAvailable Key: KAFKA-14385 URL:

[jira] [Created] (KAFKA-14384) Flaky Test SelfJoinUpgradeIntegrationTest.shouldUpgradeWithTopologyOptimizationOff

A. Sophie Blee-Goldman created KAFKA-14384: -- Summary: Flaky Test SelfJoinUpgradeIntegrationTest.shouldUpgradeWithTopologyOptimizationOff Key: KAFKA-14384 URL:

[jira] [Resolved] (KAFKA-12935) Flaky Test RestoreIntegrationTest.shouldRecycleStateFromStandbyTaskPromotedToActiveTaskAndNotRestore

[ https://issues.apache.org/jira/browse/KAFKA-12935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] A. Sophie Blee-Goldman resolved KAFKA-12935. Assignee: Lucas Brutschy Fixed again via

Re: Streams: clarification needed, checkpoint vs. position files

Hey Nick, I haven't been following the new IQv2 work very closely so take this with a grain of salt, but as far as I'm aware there's no such thing as "position files" -- the Position is just an in-memory object and is related to a user's query against the state store, whereas a checkpoint file

Re: Starting out with Kafka

Hi John, Thanks a ton. Things are looking good now. Even though Scala was present on my machine the ./gradlew compile was unable to find the Scala classes, on installing Scala plugin on IDE and then recompiling from terminal the projecting is building fine now. Thanks John and Ziming for helping

Re: [DISCUSS] KIP-883: Add delete callback method to Connector API

Thanks Greg for taking your time to review not just the KIP but also the PR. 1. You made very valid points regarding the behavior of the destroy() callback for connectors that don't follow the happy path. After thinking about it, I decided to tweak the implementation a bit and have the

Re: Starting out with Kafka

Hmm, I assume you did, but just to be sure, did you compile from the terminal before trying to build in idea? There are some generated Java classes that might be getting missed. The compile step is probably something like “compileJava compileScala compileTestJava compileTestScala” from the

Re: Starting out with Kafka

Hi, I tried both the suggestions given in the previous mail threads, all the unit tests passed except for testMuteOnOOM(). But the issue with IDE persists. I even tried invalidating the cache a few times, deleted the .bin/ and .idea/ folder and built again but there are quite few imports that

Re: [DISCUSS] KIP-875: First-class offsets support in Kafka Connect

Hi Mickael, Thanks for your feedback. This has been on my TODO list as well :) 1. That's fair! Support for altering offsets is easy enough to design, so I've added it to the KIP. The reset-after-delete feature, on the other hand, is actually pretty tricky to design; I've updated the rationale in

Re: [VOTE] KIP-866 ZooKeeper to KRaft Migration

Thanks, Colin. > never start an upgrade without first verifying the quorum configuration on > the ZK-based brokers I agree that this is a pretty big benefit. I could imagine debugging and fixing connection problems mid-migration would be a big pain. Especially if you had some brokers correctly

RE: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Two quick mistakes to clarify: When I say ClusterMetadata, I mean request 60, DescribeCluster. Also, the email subject of this entire thread should be "[DISCUSS] KIP-885: Expose Broker's Name and Version to Clients”. I must have either accidentally pasted the “Skip to end of metadata”, or did

RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Thanks for the replies David and Magnus David: 02: From a client implementation perspective, it is easier to gate features based on the max version numbers returned per request, rather than any textual representation of a string. I’m not really envisioning a client implementation trying to

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

Hi everyone, Sorry to dredge this up again. I've had a chance to start doing some testing with the WIP Pull Request, and it appears as though the secondary store solution performs rather poorly. In our testing, we had a non-transactional state store that would restore (from scratch), at a rate

Streams: clarification needed, checkpoint vs. position files

Hi everyone, I'm trying to understand how StateStores work internally for some changes that I plan to propose, and I'd like some clarification around checkpoint files and position files. It appears as though position files are relatively new, and were created as part of the IQv2 initiative, as a

Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Hi Travis and thanks for the KIP, two comments below: Den fre 11 nov. 2022 kl 13:37 skrev David Jacot : > 02: I am a bit concerned by clients that could misuse these information. > For instance, one may be tempted to rely on the version to decide whether a > feature is enabled or not. The api

Re: Starting out with Kafka

Hello Vinay, One thing I’ve noticed recently is that I have to click the “build” button in intellij before I can use the “run” or “debug” buttons. I’m not sure why. Welcome to the community! -John On Fri, Nov 11, 2022, at 02:47, deng ziming wrote: > Hello, Vinay > Kafka uses gradlew as build

Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Hi Travis, Thanks for the KIP. That seems to be a useful addition. I have a few concerns/comments: 01: Managed Kafka services do not necessarily run a specific version or may not want to expose it. I suppose that they could keep an empty string. 02: I am a bit concerned by clients that could

[jira] [Created] (KAFKA-14383) CorruptRecordException when reading data from log segment will not cause log offline

shen created KAFKA-14383: Summary: CorruptRecordException when reading data from log segment will not cause log offline Key: KAFKA-14383 URL: https://issues.apache.org/jira/browse/KAFKA-14383 Project: Kafka

[VOTE] KIP-886 Add Client Producer and Consumer Builders

Hello all, I think that adding builders for the producer and the consumer in kafka client would make it much easier for developers to instantiate new producers and consumers, especially if they are using an IDE with intellisense, and using the IDE to navigate to the documentation which could be