Re: [DISCUSS] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

Hey Konstantine, This is a very exciting and fundamental-improving KIP, thanks a lot for working on it! Have you seen KIP-345 ? I was wondering whether Connect would support the static group membership - potentially limiting the need to h

For Fun

I made this for fun :) maybe you like it https://imgflip.com/i/2r2y15

Re: [VOTE] KIP-349 Priorities for Source Topics

On 14.01.2019 02:48, n...@afshartous.com wrote: > > On reflection, it would be hard to describe the semantics of an API that > tried to address starvation by temporarily disabling prioritization, and then > oscillating back and forth. > Thus I agree that it makes sense not to try and address sta

Build failed in Jenkins: kafka-trunk-jdk8 #3312

See Changes: [wangguoz] MINOR: Put state args in correct order named repartition test (#6114) -- [...truncated 4.52 MB...] org.apache.kafka.connect.transforms.CastTest > t

Re: [VOTE] KIP-349 Priorities for Source Topics

Thanks Colin and Mathias. > On Jan 12, 2019, at 8:27 PM, Matthias J. Sax wrote: > > Thus, I would suggest to limit this KIP to the consumer only, otherwise, > the scope will be too large and this KIP will drag on even longer. If we > really want to add this to Kafka Streams, I expect a long and

Build failed in Jenkins: kafka-trunk-jdk11 #209

See Changes: [wangguoz] MINOR: Put state args in correct order named repartition test (#6114) -- [...truncated 1.39 MB...] org.apache.kafka.connect.json.JsonConverterTest

Build failed in Jenkins: kafka-trunk-jdk8 #3311

See Changes: [wangguoz] MINOR: clarify the record selection algorithm and stream-time definition -- [...truncated 2.26 MB...] org.apache.kafka.streams.test.OutputVerifier

Jenkins build is back to normal : kafka-trunk-jdk8 #3310

See

Re: KIP-213 - Scalable/Usable Foreign-Key KTable joins - Rebooted.

On 11.01.2019 21:29, John Roesler wrote: > Hi Jan, > > Thanks for the reply. > > It sounds like your larger point is that if we provide a building block > instead of the whole operation, then it's not too hard for users to > implement the whole operation, and maybe the building block is > independ

Build failed in Jenkins: kafka-trunk-jdk11 #208

See Changes: [wangguoz] MINOR: clarify the record selection algorithm and stream-time definition -- [...truncated 1.39 MB...] org.apache.kafka.connect.util.TopicAdminTes

Re: [VOTE] KIP-414: Expose Embedded ClientIds in Kafka Streams

Hi Boyang, Thanks for the feedback! 1. I did not want to expose this information since we want to have the flexibility to change its internal impls while exposing the clientIds: e.g. if in the future we've decided to let each thread use their own admin client, we'd not need to change the function

Re: [VOTE] KIP-414: Expose Embedded ClientIds in Kafka Streams

Hello Matthias, I added here since in the original KIP-345 this API was brought up once for the similar purpose. I agree this may cause more confusions than clarifications so I'll remove this. Guozhang On Sat, Jan 12, 2019 at 6:30 PM Matthias J. Sax wrote: > Thanks for the KIP. > > One side c

Re: [VOTE] - KIP-213 (new vote) - Simplified and revised.

+1 (non-binding) I have followed the discussion too and think this feature will be very helpful. Thanks Adam for staying on this. Best regards Patrik > Am 13.01.2019 um 19:55 schrieb Paul Whalen : > > +1 non binding. I haven't contributed at all to discussion but have > followed since Adam rein

Re: [VOTE] - KIP-213 (new vote) - Simplified and revised.

+1 non binding. I haven't contributed at all to discussion but have followed since Adam reinvigorated it a few months ago and am very excited about it. It would be a huge help on the project I'm working on. On Fri, Jan 11, 2019 at 9:05 AM Adam Bellemare wrote: > Thanks all - > > So far that's

Build failed in Jenkins: kafka-trunk-jdk11 #207

See Changes: [junrao] KAFKA-4453 : Added code to separate controller connections and requests -- [...truncated 1.39 MB...] org.apache.kafka.connect.transforms.TimestampCon

Build failed in Jenkins: kafka-trunk-jdk8 #3309

See Changes: [mkumar] KAFKA-7781; Add validation check for retention.ms topic property. -- [...truncated 2.26 MB...] org.apache.kafka.streams.test.OutputVerifierTest > s

[jira] [Resolved] (KAFKA-7781) Add validation check for Topic retention.ms property

[ https://issues.apache.org/jira/browse/KAFKA-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7781. -- Resolution: Fixed Assignee: Kamal Chandraprakash Fix Version/s: 2.2.0 > Add validation

Re: [DISCUSS] KIP-307: Allow to define custom processor names with KStreams DSL

Hi Matthias, The reason for overloading the methods with Materialized parameter is regarding the semantic of this class. The Materialized class allow to name a queryable store. if a name is set then it will be used both to name the state-store and the changelog-topic. If no name is given, then th

Re: [DISCUSS] KIP-382: MirrorMaker 2.0

Hey Ryanne, Sorry I am late here. Thanks much for all the work! After reading through the latest KIP and all the previous discussion, I have some questions below: 1. Currently if there is topic created with "." in the topic name, would it cause correctness issue for this KIP? For example, will co