[jira] [Created] (KAFKA-13630) Client producer reduce RecordAccumulator locks in producer thread

Jason Koch created KAFKA-13630: -- Summary: Client producer reduce RecordAccumulator locks in producer thread Key: KAFKA-13630 URL: https://issues.apache.org/jira/browse/KAFKA-13630 Project: Kafka

[jira] [Created] (KAFKA-13629) Use faster ByteUtils sizeOfXxx algorithm

Jason Koch created KAFKA-13629: -- Summary: Use faster ByteUtils sizeOfXxx algorithm Key: KAFKA-13629 URL: https://issues.apache.org/jira/browse/KAFKA-13629 Project: Kafka Issue Type: Improvement

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

See

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Sorry all, I mean KIP-851 not KIP-734. In KIP-734 we add a new OffsetSpec to AdminClient, in this KIP I just extend this OffsetSpec to GetOffsetShell. > On Jan 30, 2022, at 6:29 PM, deng ziming wrote: > > Hey all, I'm starting the voting on KIP-734. > > This supports a new OffsetSpec in GetOf

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hi Ziming, Sorry that I checked the email archive , the subject is correct. There could be something wrong in gmail grouping. Anyway, It's good to support fetch max timestamp in GetOffsetShell. I'm +1 (non-binding) BTW, you forgot

Re: [VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hi Ziming, Just a reminder, you should start a new thread with email subject starting with "[VOTE] KIP-815". Please refer to other vote email threads for example. Luke On Sun, Jan 30, 2022 at 6:37 PM deng ziming wrote: > Hey all, I'm starting the voting on KIP-734. > > This supports a n

[VOTE] KIP-815: Replace KafkaConsumer with AdminClient in GetOffsetShell

Hey all, I'm starting the voting on KIP-734. This supports a new OffsetSpec in GetOffsetShell so that we can easily determine the offset and timestamp of the message with the largest timestamp on a partition. This seems a simple change but replaced KafkaConsumer with AdminClient in GetOffset

[jira] [Resolved] (KAFKA-13612) internal topics won't be created in metadataRequest when auto.create.topics.enable=false

[ https://issues.apache.org/jira/browse/KAFKA-13612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luke Chen resolved KAFKA-13612. --- Resolution: Not A Problem > internal topics won't be created in metadataRequest when > auto.create.

[jira] [Created] (KAFKA-13628) Consider to provide a API to get the latest offset commits without respect to a specific group

Luke Chen created KAFKA-13628: - Summary: Consider to provide a API to get the latest offset commits without respect to a specific group Key: KAFKA-13628 URL: https://issues.apache.org/jira/browse/KAFKA-13628

Re: [VOTE] KIP-591: Add Kafka Streams config to set default state store

Hi John and Guozhang, Thanks for your comments. And @John, yes, you are right. The goal of the improved Materialized API is to provide a way to use im-memory store without providing the name. So, about this comment: > On the other hand, I don't see how the latter of these is more compelling than