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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.5-jdk8 #124

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

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

See Changes: [github] KAFKA-8611: update documentation for KIP-221 (#8558) -- [...truncated 6.14 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Build failed in Jenkins: kafka-trunk-jdk14 #94

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #208

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

I'm kinda hoping that we get to an approach on how to extend the Connect framework. Adding parameters in the put method is nice, and maybe works for now, but I'm not sure how scalable it is. It'd great to be able to add more functionality in the future. Couple of examples: - make the metrics

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Yeah, I had proposed to replace the "source + sink" task-level metric with "sink only" task-level metrics plus the stateful node-level ones. I completely agree that this proposal should and would look different once we complete those two proposals, ie decouple caching and consolidate suppression.

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.5-jdk8 #123

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Re: [DISCUSS] KIP-601: Configurable socket connection timeout

Dear Rajini, Thanks for all the feedbacks. They are very helpful for me to do the brainstorming. I’ve incorporated our discuss in the KIP and started a voting thread. Best, - Cheng Tan > On May 15, 2020, at 2:13 PM, Rajini Sivaram wrote: > > Hi Cheng, > > I am fine with the rest of the

[VOTE] KIP-601: Configurable socket connection timeout in NetworkClient

Hello developers, Big thanks for all the feedbacks. KIP-601 is finalized and ready for a vote. https://cwiki.apache.org/confluence/display/KAFKA/KIP-601%3A+Configurable+socket+connection+timeout+in+NetworkClient

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Just wanted to clarify that I am on board with adding the overloaded put(...) method. Thanks, Aakash On Fri, May 15, 2020 at 7:00 PM Aakash Shah wrote: > Hi Randall and Konstantine, > > As Chris and Arjun mentioned, I think the main concern is the potential > gap in which developers don't

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Randall and Konstantine, As Chris and Arjun mentioned, I think the main concern is the potential gap in which developers don't implement the deprecated method due to a misunderstanding of use cases. Using the setter method approach ensures that the developer won't break backwards compatibility

Build failed in Jenkins: kafka-trunk-jdk14 #93

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #207

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hi Sophie, I think your motivation makes sense, in fact before KIP-444 we used to have processor-node-level process latency as DEBUG which would holistically address the motivation but we removed it since it is indeed quite expensive (I do not have concrete numbers at hand, but basically you'd

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.5-jdk8 #122

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hey Guozhang, Thanks for the response. I meant to ask this earlier and forgot, but do you have any data or benchmarking results on hand for the performance hit we took due to the metrics? Or maybe better yet, on the performance we gained back by dropping some metrics? I think it would help us to

Re: [VOTE] KIP-596 Safely abort Producer transactions during application shutdown

+1. Thanks Xiang! Guozhang On Fri, May 15, 2020 at 11:37 AM John Roesler wrote: > Thanks for the KIP, Xiang! > > I’m +1 (binding) > > -John > > On Fri, May 15, 2020, at 12:08, Matthias J. Sax wrote: > > +1 (binding) > > > > -Matthias > > > > On 5/15/20 8:20 AM, Boyang Chen wrote: > > > Thanks

Build failed in Jenkins: kafka-trunk-jdk14 #92

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #206

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

Re: [VOTE] KIP-613: Add end-to-end latency metrics to Streams

Hi Sophie, Sorry I was a bit late on following up the DISCUSS thread. I still have some comment about the processor-node level metrics and left a reply on that thread. Guozhang On Fri, May 15, 2020 at 2:34 PM Sophie Blee-Goldman wrote: > Hey all, > > I think we've reached a general consensus

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hey folks, I want to make a final fight on processor-node-level metrics :) Post KIP-444 we've actually removed a lot of node-level metrics since it is too expensive to record at that level and their values are not proven worth it. Again I'd use the "we have to either enable all or none of DEBUG

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.5-jdk8 #121

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Build failed in Jenkins: kafka-trunk-jdk14 #91

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #205

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

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

See Changes: [github] KAFKA-10001: Should trigger store specific callback if it is also a -- [...truncated 3.07 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

[jira] [Created] (KAFKA-10008) Symbol not found when running Kafka Streams with RocksDB dependency on MacOS 10.13.6

Victoria Xia created KAFKA-10008: Summary: Symbol not found when running Kafka Streams with RocksDB dependency on MacOS 10.13.6 Key: KAFKA-10008 URL: https://issues.apache.org/jira/browse/KAFKA-10008

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.5-jdk8 #120

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Build failed in Jenkins: kafka-trunk-jdk14 #90

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #204

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

[jira] [Resolved] (KAFKA-1793) Allow replacing ZooKeeper with a different distributed coordination system

[ https://issues.apache.org/jira/browse/KAFKA-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-1793. --- Resolution: Won't Do This is superseeded by KIP-500

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

> @Matthias > And that's what he says about the 95th percentile! Imagine what he would say about the 50th :P I should have kept watching another 10 minutes. He gets around to covering the 50th, and let's just say he is not a fan: https://youtu.be/lJ8ydIuPFeU?t=786 On Fri, May 15, 2020 at 3:15 PM

Build failed in Jenkins: kafka-2.5-jdk8 #119

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Thanks, Sophie! I think this makes perfect sense. It will be much more intuitive to use the metric for the stated motivation this way. I’d be in favor of the proposal after this update. Thanks again for taking this on, -John On Fri, May 15, 2020, at 17:07, Sophie Blee-Goldman wrote: > Hi

Re: [DISCUSSION] KIP-418: A method-chaining way to branch KStream

Hello, John, hello Matthias! Thank you very much for your detailed feedback! - John, > It looks like you missed my reply on Apr 23rd. For some unknown reason it didn't reach my inbox, fortunately we have all the emails on the web. > 1. Can you

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hi all, I'd like to clarify/modify one aspect of this KIP, which is to record the staleness at the *completion* of the record's processing by the operator/task in question, rather than on the intake. The task-level metrics will be recorded at the sink node instead of at the source, and the

Build failed in Jenkins: kafka-trunk-jdk14 #89

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #203

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

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

See Changes: [github] KAFKA-9537 - Cleanup error messages for abstract transformations (#8090) -- [...truncated 6.14 MB...]

Re: [VOTE] KIP-607: Add Metrics to Record the Memory Used by RocksDB to Kafka Streams

+1 (binding) -Matthias On 5/15/20 11:48 AM, John Roesler wrote: > Thanks, Bruno! > > I’m +1 (binding) > > -John > > On Fri, May 15, 2020, at 11:32, Sophie Blee-Goldman wrote: >> Thanks Bruno! +1 (non-binding) >> >> Sophie >> >> On Fri, May 15, 2020 at 8:15 AM Bill Bejeck wrote: >> >>> Thanks

[VOTE] KIP-613: Add end-to-end latency metrics to Streams

Hey all, I think we've reached a general consensus on all the non-implementation details of KIP-613 so I'd like to call for a vote. https://cwiki.apache.org/confluence/display/KAFKA/KIP-613%3A+Add+end-to-end+latency+metrics+to+Streams Thanks! Sophie

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Randall, I think the problem here is that users aren't likely to implement a deprecated method, and may even remove that method from their connector after seeing that it is now deprecated. This would render that connector incompatible with older runtimes. Why deprecate a method that we don't

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

I am also happy with max/min/99/90. And I buy your naming argument about staleness vs latency. -Matthias On 5/15/20 12:24 PM, Boyang Chen wrote: > Hey Sophie, > > 90/99/min/max make sense to me. > > On Fri, May 15, 2020 at 12:20 PM Sophie Blee-Goldman > wrote: > >> @Matthias >> Regarding

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

On Fri, May 15, 2020 at 3:13 PM Arjun Satish wrote: > Couple of thoughts: > > 1. If we add new parameters to put(..), and new connectors implement only > this method, it makes them backward incompatible with older workers. I > think newer connectors may only choose to only implement the latest

[VOTE] KIP-608: Expose Kafka Metrics in Authorizer

Thanks to everyone for their input. I've incorporated the changes, and I think this is ready for voting. To summarize, the KIP simply proposes to add a feature which expose instance of Kafka Metrics in Kafka Authorizer plugin.The KIP can be found here:

Build failed in Jenkins: kafka-2.5-jdk8 #118

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Re: [DISCUSS] KIP-601: Configurable socket connection timeout

Hi Cheng, I am fine with the rest of the KIP apart from the 10s default. If no one else has any concerns about this new default, let's go with it. Please go ahead and start vote. Regards, Rajini On Fri, May 15, 2020 at 8:21 PM Cheng Tan wrote: > Dear Rajini, > > > Thanks for the reply. > >

Re: [DISCUSS] KIP-608: Add a new method to AuthorizerServerInfo Interface

Hi Jeff, Thanks for the updated KIP, looks good. Regards, Rajini On Fri, May 15, 2020 at 5:57 PM Jeff Huang wrote: > Hi David, > > Thanks for your suggestions. I updated KIP based on your comments 1,2 and > 4. For comment 3), I think the approach which Authorizer extend Monitorable > would

Re: KAFKA-10000

We got 48 tickets closed since yesterday. Great start! I am sure there is more. Please continue with more cleanup work. -Matthias On 5/14/20 9:11 PM, Guozhang Wang wrote: > Hey Matthias, thanks for calling this out in the community. > > Maybe one way to do this is to encourage everyone who

[jira] [Resolved] (KAFKA-7041) Using RocksDB bulk loading for StandbyTasks

[ https://issues.apache.org/jira/browse/KAFKA-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-7041. Resolution: Won't Fix > Using RocksDB bulk loading for StandbyTasks >

Build failed in Jenkins: kafka-trunk-jdk14 #88

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #202

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi all, I think if we're going to avoid adding methods to the SinkTaskContext due to concerns over compatibility, we might also want to ensure that the approach we follow instead doesn't have similar pitfalls. An overloaded "put", "initialize", or "start" isn't quite as troublesome with regards

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.5-jdk8 #117

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

Re: [VOTE] KIP-572: Improve timeouts and retires in Kafka Streams

Good, good. Read through the discussions, the KIP looks good to me, +1 (non-binding) On Fri, May 15, 2020 at 11:51 AM Sophie Blee-Goldman wrote: > Called out! > > Seems like gmail struggles with [...] prefixed subjects. You'd think they > would adapt > all their practices to conform to the

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Couple of thoughts: 1. If we add new parameters to put(..), and new connectors implement only this method, it makes them backward incompatible with older workers. I think newer connectors may only choose to only implement the latest method, and we are passing the compatibility problems back to

[jira] [Created] (KAFKA-10007) Kafka consumer offset reset despite recent group activity

Raman Gupta created KAFKA-10007: --- Summary: Kafka consumer offset reset despite recent group activity Key: KAFKA-10007 URL: https://issues.apache.org/jira/browse/KAFKA-10007 Project: Kafka

Build failed in Jenkins: kafka-trunk-jdk14 #87

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H23 (ubuntu) in workspace

Build failed in Jenkins: kafka-2.4-jdk8 #201

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H22 (ubuntu) in workspace

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Hi Konstantine, Thanks for the insight. In that case, I will make the appropriate changes to the KIP to support asynchronous functionality with a BiFunction. Best, Aakash On Fri, May 15, 2020 at 11:45 AM Konstantine Karantasis < konstant...@confluent.io> wrote: > Thanks for the quick response

[jira] [Created] (KAFKA-10006) Streams should not attempt to create internal topics that may exist

Sophie Blee-Goldman created KAFKA-10006: --- Summary: Streams should not attempt to create internal topics that may exist Key: KAFKA-10006 URL: https://issues.apache.org/jira/browse/KAFKA-10006

[jira] [Created] (KAFKA-10005) Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB

Guozhang Wang created KAFKA-10005: - Summary: Decouple RestoreListener from RestoreCallback and not enable bulk loading for RocksDB Key: KAFKA-10005 URL: https://issues.apache.org/jira/browse/KAFKA-10005

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

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Hey Sophie, 90/99/min/max make sense to me. On Fri, May 15, 2020 at 12:20 PM Sophie Blee-Goldman wrote: > @Matthias > Regarding tracking the 50th percentile, I'll refer you to the 4:53 mark of > the video > *you* linked: https://youtu.be/lJ8ydIuPFeU?t=293 > > And that's what he says about the

Re: [DISCUSS] KIP-601: Configurable socket connection timeout

Dear Rajini, Thanks for the reply. > e have a lot of these and I want to > understand the benefits of the proposed timeout in this case alone. We > currently have a request timeout of 30s. Would you consider adding a 10s > connection timeout? A shorter timeout (10s) at the transportation

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

@Matthias Regarding tracking the 50th percentile, I'll refer you to the 4:53 mark of the video *you* linked: https://youtu.be/lJ8ydIuPFeU?t=293 And that's what he says about the 95th percentile! Imagine what he would say about the 50th :P But seriously, since we can't seem to agree that the mean

Build failed in Jenkins: kafka-2.5-jdk8 #116

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H39 (ubuntu) in workspace

[jira] [Resolved] (KAFKA-9537) Abstract transformations in configurations cause unfriendly error message.

[ https://issues.apache.org/jira/browse/KAFKA-9537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-9537. -- Fix Version/s: 2.5.1 2.4.2 2.6.0 Reviewer:

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

On Fri, May 15, 2020 at 1:45 PM Konstantine Karantasis < konstant...@confluent.io> wrote: > Thanks for the quick response Aakash. > > To your last point, modern APIs like this tend to be asynchronous (see > admin, producer in Kafka) and such definition results in more expressive > and well

Build failed in Jenkins: kafka-trunk-jdk14 #86

See Changes: -- Started by an SCM change Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H38 (ubuntu) in workspace

Build failed in Jenkins: kafka-trunk-jdk14 #85

See Changes: [github] KAFKA-9996: Upgrade zookeeper to 3.5.8 (#8674) -- [...truncated 4.49 MB...] org.apache.kafka.common.metrics.MetricsTest > testRemoveInactiveMetrics

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

See Changes: -- Started by an SCM change Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H28 (ubuntu) in workspace

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

See Changes: [github] KAFKA-9996: Upgrade zookeeper to 3.5.8 (#8674) -- [...truncated 4.93 MB...] kafka.admin.ConfigCommandTest >

Re: [VOTE] KIP-586: Deprecate commit records without record metadata

This KIP is now accepted. The vote has been open for >72 hours (actually ~4 weeks), and we have three binding +1s (Konstantine, Gwen, me), one non-binding +1 (Mario), and no -1 votes. Thanks, everyone! On Thu, May 14, 2020 at 6:42 PM Gwen Shapira wrote: > +1 (binding) > > Makes a lot of sense

Re: [VOTE] KIP-572: Improve timeouts and retires in Kafka Streams

Called out! Seems like gmail struggles with [...] prefixed subjects. You'd think they would adapt all their practices to conform to the Apache Kafka mailing list standards, but no! +1 (non-binding) by the way On Fri, May 15, 2020 at 11:46 AM John Roesler wrote: > Hi Boyang, > > It is a

Re: [VOTE] KIP-607: Add Metrics to Record the Memory Used by RocksDB to Kafka Streams

Thanks, Bruno! I’m +1 (binding) -John On Fri, May 15, 2020, at 11:32, Sophie Blee-Goldman wrote: > Thanks Bruno! +1 (non-binding) > > Sophie > > On Fri, May 15, 2020 at 8:15 AM Bill Bejeck wrote: > > > Thanks for the KIP! > > > > +1 (binding) > > > > -Bill > > > > On Fri, May 15, 2020 at

Build failed in Jenkins: kafka-2.5-jdk8 #115

See Changes: [ismael] KAFKA-9996: Upgrade zookeeper to 3.5.8 (#8674) -- [...truncated 2.05 MB...] org.apache.kafka.streams.integration.GlobalThreadShutDownOrderTest >

Re: [VOTE] KIP-572: Improve timeouts and retires in Kafka Streams

Hi Boyang, It is a separate thread, and you have just revealed yourself as a gmail user ;) (Gmail sometimes conflates vote and discuss threads for no apparent reason ) -John On Fri, May 15, 2020, at 13:39, Boyang Chen wrote: > Hey Matthias, should this be on a separate VOTE thread? > > On

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Thanks for the quick response Aakash. To your last point, modern APIs like this tend to be asynchronous (see admin, producer in Kafka) and such definition results in more expressive and well defined APIs. What you describe is easily an opt-in feature for the connector developer. At the same

Re: [VOTE] KIP-572: Improve timeouts and retires in Kafka Streams

Hey Matthias, should this be on a separate VOTE thread? On Fri, May 15, 2020 at 11:38 AM John Roesler wrote: > Thanks, Matthias! > > I’m +1 (binding) > > -John > > On Fri, May 15, 2020, at 11:55, Matthias J. Sax wrote: > > Hi, > > > > I would like to start the vote on KIP-572: > > > > >

Re: [VOTE] KIP-572: Improve timeouts and retires in Kafka Streams

Thanks, Matthias! I’m +1 (binding) -John On Fri, May 15, 2020, at 11:55, Matthias J. Sax wrote: > Hi, > > I would like to start the vote on KIP-572: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-572%3A+Improve+timeouts+and+retries+in+Kafka+Streams > > > -Matthias > > >

Re: [VOTE] KIP-596 Safely abort Producer transactions during application shutdown

Thanks for the KIP, Xiang! I’m +1 (binding) -John On Fri, May 15, 2020, at 12:08, Matthias J. Sax wrote: > +1 (binding) > > -Matthias > > On 5/15/20 8:20 AM, Boyang Chen wrote: > > Thanks for the KIP Xiang, +1 (non-binding) from me! > > > > On Fri, May 15, 2020 at 2:05 AM 张祥 wrote: > > >

Re: [VOTE] KIP-437: Custom replacement for MaskField SMT

This KIP is now accepted. The vote has been open for >72 hours (actually almost 5 months), and we have three binding +1s (Konstantine, Bill, me), two non-binding +1s (Yu, Andrew), and no -1 votes. Thanks, everyone! On Fri, May 15, 2020 at 9:07 AM Bill Bejeck wrote: > Thanks for the KIP. > >

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Thanks for the additional feedback. I see the benefits of adding an overloaded put(...) over alternatives and I am on board going forward with this approach. It will definitely set forth a contract of where the reporter will be used with better aesthetics. The original idea of going with a

Re: [VOTE] KIP-605 - Expand Connect Worker Internal Topic Settings

This KIP is now accepted. The vote has been open for >72 hours (actually 8 days), and we have four binding +1s (Konstantine, Bill, John, me), one non-binding +1 (Chris), and no -1 votes. Thanks, everyone! On Fri, May 15, 2020 at 12:13 PM John Roesler wrote: > Thanks for the KIP, Randall! > >

Re: [DISCUSS] KIP-613: Add end-to-end latency metrics to Streams

Thanks for the KIP, Sophie, this will be a useful metric to add. Regarding tracking min, I think it could be valuable for users to discern which part of their topologies are more efficient since this is a task-level metric. I realize everyone seems to be on board with including min anyway, but

Re: [VOTE] KIP 585: Filter and conditional SMTs

+1 (binding) Thanks Tom. Konstantine On Fri, May 15, 2020 at 5:03 AM Andrew Schofield wrote: > +1 (non-binding) > > Thanks for the KIP. This will be very useful. > > Andrew Schofield > > On 13/05/2020, 10:14, "Tom Bentley" wrote: > > Hi, > > I'd like to start a vote on KIP-585:

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

See Changes: [github] KAFKA-9996: Upgrade zookeeper to 3.5.8 (#8674) -- [...truncated 3.07 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

Re: [VOTE] KIP-606: Add Metadata Context to MetricsReporter

Thanks for the proposal, Xavier. +1(binding) -Bill On Fri, May 15, 2020 at 1:41 PM John Roesler wrote: > Thanks for the KIP, Xavier! > > I'm +1 (binding) as well. > > Thanks, > -John > > On Thu, May 14, 2020, at 17:07, Randall Hauch wrote: > > +1 (binding) > > > > Thanks for the proposal,

Re: [VOTE] KIP-606: Add Metadata Context to MetricsReporter

Thanks for the KIP, Xavier! I'm +1 (binding) as well. Thanks, -John On Thu, May 14, 2020, at 17:07, Randall Hauch wrote: > +1 (binding) > > Thanks for the proposal, Xavier. > > On Wed, May 13, 2020 at 4:10 PM Gwen Shapira wrote: > > > +1 (binding) > > Thanks for the proposal, Xavier. > > >

Re: [VOTE] KIP-221: Enhance KStream with Connecting Topic Creation and Repartition Hint

Thanks Levani! I took the liberty to update the KIP accordingly, because so far no concerns were raised about the change. Also assigned the ticket to myself (let me know if you want to work on it instead). We should get the change into 2.6 release. -Matthias On 5/15/20 1:34 AM, Levani

Re: [DISCUSS] KIP-610: Error Reporting in Sink Connectors

Small correction. I didn't mean to declare the new method `abstract`. I agree with Randall's suggestion to give it a default implementation that will call the old `put` and at the same time deprecate the old `put`. Konstantine On Fri, May 15, 2020 at 10:19 AM Konstantine Karantasis <

[jira] [Resolved] (KAFKA-7174) Improve version probing of subscription info

[ https://issues.apache.org/jira/browse/KAFKA-7174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-7174. -- Resolution: Fixed > Improve version probing of subscription info >

  1   2   >