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

See Changes: -- [...truncated 501279 lines...] [2022-08-13T05:36:20.026Z] [2022-08-13T05:36:20.026Z] KStreamAggregationIntegrationTest > shouldAggregateSlidingWindows(Tes

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

Hey John, Thanks for the vote. I added the reason for the rejection of the alternatives. The first one is basically an option to broadcast to all partitions which I felt was restrictive. Instead the KIP allows multicasting to 0-N partitions based upon the partitioner implementation. Thanks! Sagar

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

See

Re: [DISCUSS] KIP-862: Implement self-join optimization

Thanks for the KIP, Vicky! Re 1/2, I agree with what you both worked out. Re 3: It sounds like you were able to preserve backward compatibility, so I don’t think you need to add any new configs. I think you can just switch it on if people specify “all”. Thanks! -John On Thu, Aug 11, 2022,

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

Thanks, Sagar! I’m +1 (binding) Can you add a short explanation to each rejected alternative? I was wondering why we wouldn’t provide an overloaded to()/addSink() (the first rejected alternative), and I had to look back at the Streams code to see that they both already accept the partitioner (

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

See Changes: -- [...truncated 487077 lines...] [2022-08-12T19:32:53.582Z] org.apache.kafka.streams.integration.TableTableJoinIntegrationTest > testOuter[caching enabled = fal

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

See

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

Awesome, thanks Robert! Will work on updated the proposal around this. Also, @Chris Egerton if you have any feedback about this, would be much appreciated. Cheers, Jorge. On Fri, 12 Aug 2022 at 18:45, Robert Yokota wrote: > Hi Jorge, > > Yes, to escape a backtick I would recommend a backslash.

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

Hi Jorge, Yes, to escape a backtick I would recommend a backslash. For example, MySQL allows identifiers to be surrounded with single quotes, double quotes, or backticks, and they use backslash to escape. Jsonata went with primarily backticks as they are less common in strings that appear in JSO

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

See

[jira] [Resolved] (KAFKA-13959) Controller should unfence Broker with busy metadata log

[ https://issues.apache.org/jira/browse/KAFKA-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jose Armando Garcia Sancio resolved KAFKA-13959. Resolution: Fixed > Controller should unfence Broker with busy met

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

Thanks Robert! And sorry for the late reply. That's a great catch and will require the current proposal to be updated. Using back-ticks is a good proposal. Though, the challenge we got is that JSON allows really any character into attribute names, including back-ticks. I wonder what's the best ap

[jira] [Created] (KAFKA-14165) ConfigTransformer.DEFAULT_PATTERN fails on Windows platform

Gabor Andras created KAFKA-14165: Summary: ConfigTransformer.DEFAULT_PATTERN fails on Windows platform Key: KAFKA-14165 URL: https://issues.apache.org/jira/browse/KAFKA-14165 Project: Kafka

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Thank you Guozhang/David for the feedback. Looks like there's agreement on using separate APIs for Connect. I would revisit the doc and see what changes are to be made. Thanks! Sagar. On Tue, Aug 9, 2022 at 7:11 PM David Jacot wrote: > Hi Sagar, > > Thanks for the feedback and the document. Tha

Re: [DISCUSS] KIP-848: The Next Generation of the Consumer Rebalance Protocol

Hi all, Thanks again for all the very good feedback so far. I have addressed, I think, all the outstanding points. Here are the main updates: * I have introduced STALE_MEMBER_EPOCH to differentiate it from the fatal FENCED_MEMBER_EPOCH error. * I have introduced topic ids in the OffsetCommit/Off