[jira] [Created] (KAFKA-13701) Pin background worker threads for certain background work (ex: UnifiedLog.flush())

Kowshik Prakasam created KAFKA-13701: Summary: Pin background worker threads for certain background work (ex: UnifiedLog.flush()) Key: KAFKA-13701 URL: https://issues.apache.org/jira/browse/KAFKA-13701

[jira] [Created] (KAFKA-13700) Kafka reporting corrupted block message.

Uday Bhaskar created KAFKA-13700: Summary: Kafka reporting corrupted block message. Key: KAFKA-13700 URL: https://issues.apache.org/jira/browse/KAFKA-13700 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-13699) ProcessorContext does not expose Stream Time

Shay Lin created KAFKA-13699: Summary: ProcessorContext does not expose Stream Time Key: KAFKA-13699 URL: https://issues.apache.org/jira/browse/KAFKA-13699 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi, Artem, Thanks for the reply. A few more comments. 1. Since we control the implementation and the usage of DefaultPartitioner, another way is to instantiate the DefaultPartitioner with a special constructor, which allows it to have more access to internal information. Then we could just

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

See Changes: -- [...truncated 368092 lines...] [2022-02-28T19:34:26.638Z] streams-5: SMOKE-TEST-CLIENT-CLOSED [2022-02-28T19:34:28.418Z] [2022-02-28T19:34:28.418Z]

Re: [DISCUSS] KIP-821: Connect Transforms support for nested structures

Thank you, Chris! and sorry for the delayed response. Please, find my comments below: On Mon, 14 Feb 2022 at 17:34, Chris Egerton wrote: > Hi Jorge, > > Thanks for the KIP! I'd love to see support for nested fields added to the > out-of-the-box SMTs provided with Connect. Here are my initial

[jira] [Resolved] (KAFKA-13542) Utilize the new Consumer#enforceRebalance(reason) API in Streams

[ https://issues.apache.org/jira/browse/KAFKA-13542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13542. --- Resolution: Fixed > Utilize the new Consumer#enforceRebalance(reason) API in Streams >

Re: [DISCUSS] KIP-813 Shared State Stores

Updated the KIP to be more aligned with global state store function names. If I remember correctly during restore the processor will not be used right? I think this might provide issues if your processor is doing a projection of the data. Either way, I would not add that into this KIP since it

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

Thank you David, I have already updated the KIP. The PR will be finished soon. -- Ziming Deng > On Feb 28, 2022, at 6:38 PM, David Jacot wrote: > > Thanks. Could you update the KIP to incorporate > Mickael's feedback? Ping me once the PR is > updated, I will finish reviewing it. > > Best, >

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

Thanks. Could you update the KIP to incorporate Mickael's feedback? Ping me once the PR is updated, I will finish reviewing it. Best, David On Mon, Feb 28, 2022 at 11:33 AM deng ziming wrote: > > Hi all, > > Since it’s a pretty minor KIP, I think we can pass the vote with: > - 4 +1(binding)

Re: [VOTE] KIP-815: Support max-timestamp in GetOffsetShell

Hi all, Since it’s a pretty minor KIP, I think we can pass the vote with: - 4 +1(binding) votes (Luke, David, Mickael and John) Thanks to all that participated in the discussion and voting, -- Ziming Deng > On Feb 22, 2022, at 2:56 PM, David Jacot wrote: > > For reference, here is the KIP: