The most appropriate version in the production

Hi all, Could you please tell me which version is the most appropriate in the production? There are our several requirements : 1. Most stable 2. More latest 3. Easy to upgrade 4. Support the 500GB every day in the production (not the test). 5. 2.2.2 or 2.6.2 and more? Thanks for your

Re: [VOTE] KIP-721: Enable connector log contexts in Connect Log4j configuration

+1 (Non-binding) Thanks, Dongjin On Thu, May 6, 2021 at 3:19 AM Randall Hauch wrote: > I'd like to start a vote on KIP-721: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-721%3A+Enable+connector+log+contexts+in+Connect+Log4j+configuration > > +1 (binding) from myself. > > Thanks,

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

See

[jira] [Resolved] (KAFKA-12536) Add Instant-based methods to ReadOnlySessionStore

[ https://issues.apache.org/jira/browse/KAFKA-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-12536. -- Fix Version/s: 3.0.0 Resolution: Fixed > Add

[jira] [Resolved] (KAFKA-10434) Remove deprecated methods on WindowStore

[ https://issues.apache.org/jira/browse/KAFKA-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-10434. -- Resolution: Fixed > Remove deprecated methods on WindowStore

Re: [DISCUSS] KIP-618: Atomic commit of source connector records and offsets

Hi Tom, Thanks for taking a look! Really appreciate it. Answers below: 1. a) This is possible, but it would likely require reworking the rebalance protocol, and would not provide comprehensive guarantees about exactly-once delivery. If the group coordination protocol used for rebalancing is also

[jira] [Resolved] (KAFKA-12451) Remove deprecation annotation on long-based read operations in WindowStore

[ https://issues.apache.org/jira/browse/KAFKA-12451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-12451. -- Fix Version/s: 3.0.0 Resolution: Fixed

[jira] [Resolved] (KAFKA-12450) Remove deprecated methods from ReadOnlyWindowStore

[ https://issues.apache.org/jira/browse/KAFKA-12450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jorge Esteban Quilcate Otoya resolved KAFKA-12450. -- Fix Version/s: 3.0.0 Resolution: Fixed > Remove

Re: [VOTE] KIP-730: Producer ID generation in KRaft mode

Colin, thanks for the feedback. I like the record name you proposed. I've also updated the first paragraph in the Controller section to: In both ZK and KRaft modes, the controller will now be responsible for > generating new blocks of IDs and persisting the latest generated block. In > ZK mode,

[jira] [Created] (KAFKA-12763) NoSuchElementException during kafka-log-start-offset-checkpoint

Igor Soarez created KAFKA-12763: --- Summary: NoSuchElementException during kafka-log-start-offset-checkpoint Key: KAFKA-12763 URL: https://issues.apache.org/jira/browse/KAFKA-12763 Project: Kafka

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

See

[jira] [Created] (KAFKA-12762) Use connection timeout when polling the network for new connections

Mickael Maison created KAFKA-12762: -- Summary: Use connection timeout when polling the network for new connections Key: KAFKA-12762 URL: https://issues.apache.org/jira/browse/KAFKA-12762 Project:

Re: Fetching rows from DB and insert it into multiple topics

Hi, I’d look into Kafka streams https://kafka.apache.org/documentation/streams/. You could use your connector to dump all records into a single topic and then write a streams application that can use arbitrary logic to route records to different downstream topics. A nice benefit, in my opinion,

Fetching rows from DB and insert it into multiple topics

Hi, Can you please advise on the following: current behaviour 1)I have records in DB 2)Using JDBC connector I am taking out the records from DB and sends them into a specific topic expected behavior take out the records from DB and push them to a different topics based on criteria from the

[jira] [Resolved] (KAFKA-10420) group instance id Optional.empty failed due to UNKNOWN_MEMBER_ID, resetting generation when running kafka client 2.6 against broker 2.3.1

[ https://issues.apache.org/jira/browse/KAFKA-10420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Kaszuba resolved KAFKA-10420. Resolution: Duplicate > group instance id Optional.empty failed due to UNKNOWN_MEMBER_ID,

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

See

[RESULTS] [VOTE] Release Kafka version 2.7.1

This vote passes with 5 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * John Roesler * Bill Bejeck * Randall Hauch Community: * Israel Ekpo * Satish Duggana 0 votes * No votes -1 votes * No votes Vote thread:

Re: [VOTE] KIP-699: Update FindCoordinator to resolve multiple Coordinators at a time

Hi Sanjana, Sorry for the late reply. I hope to have a draft PR next week. Thanks On Tue, May 4, 2021 at 11:11 PM Sanjana Kaundinya wrote: > > Hi Mickael, > > Just wanted to ping the thread to inquire if you’ve made any progress on the > implementation. I was planning on doing the

[jira] [Created] (KAFKA-12761) Consumer offsets are deleted 7 days after last offset instead of EMPTY status

Tomasz Kaszuba created KAFKA-12761: -- Summary: Consumer offsets are deleted 7 days after last offset instead of EMPTY status Key: KAFKA-12761 URL: https://issues.apache.org/jira/browse/KAFKA-12761

Re: [DISCUSS] KIP-334 Include partitions in exceptions during consumer record deserialization/validation (Round 2)

Jason, Colin, and Mathias, do you have any comments on the KIP as it stands now? Thank you. Sarwar On Fri, 23 Apr 2021 at 10:12, Sarwar Bhuiyan wrote: > Hi all, > > I'm reviving this discussion after perusing the vote thread created by > Stan. I believe the KIP is already revised to include