Re: [VOTE] 4.0.0 RC0

If the purpose of this is not to vote but just to evaluate the RC then I think it would be better to not use the [VOTE] tag for the subject as that is super confusing. On Mon, Feb 24, 2025 at 10:45 AM Ismael Juma wrote: > Hi Mickael, > > This was addressed in the original message: > > "This is t

Re: KIPs being posted to the wrong section on the wiki

Ok, sounds good, thanks. I went ahead and cleaned things up and moved those KIPs to the right section. On Wed, Jan 15, 2025 at 8:21 PM Chris Egerton wrote: > Hi Chris, > > Yes, this is fine--have at it. > > Cheers, > > Other Chris > > On Wed, Jan 15, 2025

KIPs being posted to the wrong section on the wiki

Hey Everyone, Recently I've noticed a trend of new KIPs that are under discussion or still being worked on (in draft) being posted to the "adopted" section at the top of the page which is very confusing. This seems to be getting worse and worse. I hesitate to modify the wiki page and move someone

Re: PR review request for KIP-1032

dress it > quickly. > Best, > Chia-Ping > > > Christopher Shannon 於 2024年10月16日 週三 > 下午11:00寫道： > > > Can someone review https://github.com/apache/kafka/pull/16754 when they > > get > > a chance? > > > > It's for KIP-1032 and upgrades to Jaka

PR review request for KIP-1032

Can someone review https://github.com/apache/kafka/pull/16754 when they get a chance? It's for KIP-1032 and upgrades to Jakarta, JavaEE 10 and Jetty 12. With Kafka 3.9.0 being voted on, Kafka 4.0 should not be too much longer so it would be good to get this merged in. Thanks, Chris

Re: New release branch 3.9

One option is to just have a separate 4.0 branch for development to not block work on new features. With Apache Accumulo we have a similar situation where we have a separate branch (ironically also 4.0) that we are calling "elasticity" that is a long running br

Re: [VOTE]: KIP-1032: Upgrade to Jakarta and JavaEE 10 in Kafka 4.0

Hi Everyone, I forgot to add my explicit +1 (non-binding) as well. The vote passes with: * 3 binding votes (Chris Egerton, Mickael Maison, Greg Harris) * 1 non-binding vote (Christopher Shannon) I'll update the wiki. I should have some time coming up to work on a PR for this if no one

Re: [VOTE]: KIP-1032: Upgrade to Jakarta and JavaEE 10 in Kafka 4.0

is > unfortunately a > > way in which one of our dependencies "leaks through" our API, and makes > > this a necessity. > > Connect and MirrorMaker2 can follow the broker's lead on setting Java 17 > as > > the minimum version. > > > > +1 (bindin

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

The KIP has been updated to include the changes to the ConnectRestExtensionContext. On Tue, Jul 9, 2024 at 7:16 PM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Thanks, I missed that, I can update the KIP tomorrow to include that. > > Chris > > On Tue, J

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

/apache/kafka/connect/rest/ConnectRestExtensionContext.java#L22 > > Cheers, > > Other Chris > > On Tue, Jul 9, 2024 at 3:40 PM Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > Hi Chris, > > > > I can make those changes. For number

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

to be used". This is a pretty big "if". My > understanding is that we will definitely be using Jetty 12.x; can we remove > the "if" or is it still up for debate whether we'll do that switch for > Connect? > > Cheers, > > Other Chris > > On Tue,

[VOTE]: KIP-1032: Upgrade to Jakarta and JavaEE 10 in Kafka 4.0

Hi Everyone, I'd like to call a vote on https://cwiki.apache.org/confluence/display/KAFKA/KIP-1032%3A+Upgrade+to+Jakarta+and+JavaEE+10+in+Kafka+4.0 This KIP upgrades to the latest Jakarta API and newest version of Jetty 12 and removes the deprecated javax APIs. It also bumps the required version

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

> > On Tue, May 14, 2024 at 9:07 AM Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > I just wanted to bump this and see if anyone had more feedback before > > trying to call a vote for this for 4.0? > > > > Chris > > > > On

Re: [DISCUSS] Apache Kafka 3.8.0 release

is this where I ask to join? On Thu, Jun 13, 2024 at 1:20 PM Greg Harris wrote: > Hi Sophie and Justine, > > I share your concerns about delaying 3.8 in order to give the Kraft KIPs > more time for implementation. I raised them in the discussion for KIP-1012 > [1]: > > > I think there is a > >

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

I just wanted to bump this and see if anyone had more feedback before trying to call a vote for this for 4.0? Chris On Mon, Apr 1, 2024 at 3:41 PM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Greg, > > 1. Ok sounds good we can target JDK 17 in this KIP if we de

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

need to be mentioned in the KIP itself. I > have seen people adopt changes from un-merged PRs after the original > contributor has lost interest, while still crediting the original > contributor for their portion of the changes. If you're doing this, > then it's ultimate

Re: [DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

900d9f85e6acd9a09bd04969afa46261/src/main/java/com/loobpack/data/kafka/connect/healthcheck/extension/HealthCheckConnectRestExtension.java#L9 > > > > I figure that adopting this KIP would mean that the Debezium project > > would be forced to bump their major version 3.0 to be comp

[DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

Hi, I'm proposing a KIP for Kafka 4.0 to upgrade to to Jakarta and JavaEE 9 APIs. This will also upgrade dependencies like Jetty and move away from the depcrated javax namespace to be in line with other libraries and frameworks. There was some initial

[jira] [Created] (KAFKA-16437) Upgrade to Jakarta and JavaEE 9 in Kafka 4.0 (KIP-1032)

Christopher L. Shannon created KAFKA-16437: -- Summary: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0 (KIP-1032) Key: KAFKA-16437 URL: https://issues.apache.org/jira/browse/KAFKA-16437 Project

Re: [DISCUSS] Jakarta and Java EE 9/10 support in Kafka 4.0

Hi Christopher, > > Thanks for raising this. Moving to the new namespace makes sense - would > you be willing to submit a KIP? The point you raised regarding Jetty 11 EOL > and Jetty 12 requiring Java 17 is a good one and is worth discussing the > trade-offs in more detail. I original

Re: [DISCUSS] Jakarta and Java EE 9/10 support in Kafka 4.0

be that could be reopened? Also, I assume this would need a KIP to proceed. Chris [1] https://github.com/jetty/jetty.project/issues/10485 [2] https://github.com/apache/kafka/pull/10176 On Tue, Mar 26, 2024 at 1:11 PM Greg Harris wrote: > Hey Christopher, > > Thank you for explain

Re: [DISCUSS] Jakarta and Java EE 9/10 support in Kafka 4.0

Kafka 4.0 with a Jetty version that is already end of life doesn't make sense to me. I know that Connect supports isolated classloaders for connectors but that of course is not the same as different Java versions. Chris On Tue, Mar 26, 2024 at 11:33 AM Greg Harris wrote: > Hi Christopher!

[DISCUSS] Jakarta and Java EE 9/10 support in Kafka 4.0

Is this already being planned for version 4.0? If not, I strongly thing it should be. Kafka is currently using the old long deprecated javax apis which is going to continue to cause issues [1] for people as more and more things are updated to use Jakarta. With the bump to require JDK 17 for versi

Re: [DISCUSS] Minimum constraint for segment.ms

I think it's a great idea to raise a KIP to look at adjusting defaults and minimum/maximum config values for version 4.0. As pointed out, the minimum values for segment.ms and segment.bytes don't make sense and would probably bring down a cluster pretty quickly if set that low, so version 4.0 is a

Re: [DISCUSS] Road to Kafka 4.0

I think JBOD definitely needs to be before 4.0. That has been a blocker issue this entire time for me and my team and I'm sure others. While Kraft has been technically "production ready" for a while, I haven't been able to upgrade because of missing JBOD support. On Wed, Oct 11, 2023 at 12:15 PM I

[jira] [Created] (KAFKA-15006) kafka-get-offsets.sh returns 0 for earliest offset on a compacted topic

Christopher Auston created KAFKA-15006: -- Summary: kafka-get-offsets.sh returns 0 for earliest offset on a compacted topic Key: KAFKA-15006 URL: https://issues.apache.org/jira/browse/KAFKA-15006

[jira] [Created] (KAFKA-14268) When aggregating on a KGroupedStream allow an InitializerWithKey

Christopher Meier created KAFKA-14268: - Summary: When aggregating on a KGroupedStream allow an InitializerWithKey Key: KAFKA-14268 URL: https://issues.apache.org/jira/browse/KAFKA-14268 Project

Re: Request for contributor permissions

Brilliant, thanks Chris! On Sun, Sep 25, 2022 at 5:01 PM Chris Egerton wrote: > Hi Chris, > > You're all set. > > Cheers, > > Chris > > On Sat, Sep 24, 2022 at 4:51 AM Christopher Razavian < > chris.pooya.razav...@gmail.com> wrote: > > >

Request for contributor permissions

Hello, I'd like to request for contributor permissions. JIRA ID: pooya72. Thank you. Regards, Chris

Re: [VOTE] 3.2.1 RC3

+1 (non binding) I built from source and ran through some of the tests including all the connect runtime tests. I verified that KAFKA-14079 was included and the fix looked good in my tests. On Thu, Jul 21, 2022 at 9:15 PM David Arthur wrote: > Hello Kafka users, developers and client-developers

Re: [DISCUSS] Apache Kafka 3.3.0 Release

s coming up soon (the release > doc currently has it at July 20th), it'd be nice if we could get some eyes > on the PR for 3.2.1 and, if that looks good, a PR for trunk and 3.3.0. > > Cheers, > > Chris > > On Sat, Jul 16, 2022 at 12:31 PM Christopher Shannon < &g

Re: [DISCUSS] Apache Kafka 3.2.1 release

uot;all". > > Cheers, > > Chris > > On Sat, Jul 16, 2022 at 12:26 PM Christopher Shannon < > christopher.l.shan...@gmail.com> wrote: > > > HI, > > > > I think I found a memory leak that was introduced in 3.2.0 in a Connector > > SourceTask.

Re: [DISCUSS] Apache Kafka 3.3.0 Release

There is a bug I found that I think is worthwhile fixing in 3.3.0 (I also sent a note to 3.2.1 thread): https://issues.apache.org/jira/browse/KAFKA-14079 On Thu, Jul 14, 2022 at 7:56 PM Jason Gustafson wrote: > Hey Jose, > > Thanks for volunteering to manage the release! KIP-833 is currently slo

Re: [DISCUSS] Apache Kafka 3.2.1 release

HI, I think I found a memory leak that was introduced in 3.2.0 in a Connector SourceTask. I created a JIRA: https://issues.apache.org/jira/browse/KAFKA-14079 and small PR with a fix: https://github.com/apache/kafka/pull/12412 I think this should be included in 3.2.1. It should also go into 3.3.0

[jira] [Created] (KAFKA-14079) Source task develops memory leak if "error.tolerance" is set to "all"

Christopher L. Shannon created KAFKA-14079: -- Summary: Source task develops memory leak if "error.tolerance" is set to "all" Key: KAFKA-14079 URL: https://issues.apache.org/jir

Re: [DISCUSS] KIP-729 Custom validation of records on the broker prior to log append

ation of this API. > >>>> > >>>> I’m ready to drive the implementation of this API. > >>>> It seems very useful to me. > >>>> > >>>>> 30 июня 2021 г., в 18:04, Nikolay Izhikov > >>>> написал(а): > >>

Re: [VOTE] KIP-779: Allow Source Tasks to Handle Producer Exceptions

+1 (non-binding). This looks good to me and will be useful as a way to handle producer errors. On Mon, Nov 8, 2021 at 8:55 AM Knowles Atchison Jr wrote: > Good morning, > > I'd like to start a vote for KIP-779: Allow Source Tasks to Handle Producer > Exceptions: > > > https://cwiki.apache.org/co

Re: [DISCUSS] KIP-779: Allow Source Tasks to Handle Producer Exceptions

I also would find this feature useful to handle errors better, does anyone have any comments or feedback? On Mon, Oct 11, 2021 at 8:52 AM Knowles Atchison Jr wrote: > Good morning, > > Bumping this for visibility. I would like this to go into the next release. > KIP freeze is Friday. > > Any co

Becoming a contributor

Hi I would like to contribute if possible

Re: Ensuring that Kafka message is persisted after acknowledgement

You can control fsync with two properties: https://kafka.apache.org/documentation/#topicconfigs_flush.messages https://kafka.apache.org/documentation/#topicconfigs_flush.ms On Wed, Aug 25, 2021 at 10:39 AM Kunal Goyal wrote: > Hello, > > We are exploring using Kafka for our application. Our re

[jira] [Created] (KAFKA-13077) Replication failing after unclean shutdown of ZK and all brokers

Christopher Auston created KAFKA-13077: -- Summary: Replication failing after unclean shutdown of ZK and all brokers Key: KAFKA-13077 URL: https://issues.apache.org/jira/browse/KAFKA-13077 Project

Re: [DISCUSS] KIP-729 Custom validation of records on the broker prior to log append

I would find this feature very useful as well as adding custom validation to incoming records would be nice to prevent bad data from making it to the topic. On Wed, Apr 7, 2021 at 7:03 PM Soumyajit Sahu wrote: > Thanks Colin! Good call on the ApiRecordError. We could use > InvalidRecordException

Re: [DISCUSS] KIP-755: Add new AUTO_CREATE ACL for auto topic creation

if it's a super user or not which is better but not perfect. On Wed, Jun 23, 2021 at 8:49 AM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Hi Ismael, > > Thanks for the response. > > I initially tried to use a create topic policy but the issue with the >

Re: [DISCUSS] KIP-755: Add new AUTO_CREATE ACL for auto topic creation

going with the different approach of providing the user principal as part of the metadata to the CreateTopicPolicy and AlterConfigPolicies. Chris On Wed, Jun 23, 2021 at 8:27 AM Ismael Juma wrote: > Hi Christopher, > > Thanks for the KIP. Have you considered using create topic policies to

Re: [DISCUSS] KIP-755: Add new AUTO_CREATE ACL for auto topic creation

Hi Everyone, It has been a couple weeks so figured I'd ping one last time to see if anyone had any interest in this. This feature would be quite useful to me (and hopefully others) and should be a pretty small change and backwards compatible. Chris On Fri, Jun 11, 2021 at 9:24 AM Christ

Re: [DISCUSS] KIP-755: Add new AUTO_CREATE ACL for auto topic creation

Does anyone have any thoughts or feedback on this KIP? On Tue, Jun 8, 2021 at 2:09 PM Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > Hi Everyone, > > I'd like to propose KIP-755: Add new AUTO_CREATE ACL for auto topic > creation > > The K

[DISCUSS] KIP-755: Add new AUTO_CREATE ACL for auto topic creation

Hi Everyone, I'd like to propose KIP-755: Add new AUTO_CREATE ACL for auto topic creation The KIP can be found here: https://cwiki.apache.org/confluence/display/KAFKA/KIP-755%3A+Add+new+AUTO_CREATE+ACL+for+auto+topic+creation I submitted the following PR: https://github.com/apache/kafka/pull/108

[jira] [Created] (KAFKA-12916) Add new AUTO_CREATE ACL for auto topic creation

Christopher L. Shannon created KAFKA-12916: -- Summary: Add new AUTO_CREATE ACL for auto topic creation Key: KAFKA-12916 URL: https://issues.apache.org/jira/browse/KAFKA-12916 Project: Kafka

Re: Kafka Advisory Topic

; > themselves. I hope the proposal can include a few example scenarios to > > help us reason about the experience. > > > > Knowlton, is this something you want to pick up? > > > > Gwen > > > > On Thu, Jan 21, 2021 at 6:05 AM Christopher Shanno

Re: Kafka Advisory Topic

Hi, I am on the ActiveMQ PMC and I think this is a very good idea to have a way to do advisories/notifications/events (whatever you want to call it). In ActiveMQ classic you have advisories and in Artemis you have notifications. Having management messages that can be subscribed to in real time is

Re: [DISCUSS] KIP-640 Add log compression analysis tool

Bump. I'd like to gather more feedback on this! Chris On 2020/08/17 20:23:51, "Christopher Beard (BLOOMBERG/ 919 3RD A)" wrote: > Hi everyone, > > I would like to start a discussion on KIP-640: > https://cwiki.apache.org/confluence/display/KAFKA/KIP-640%3A+Add+lo

Re: [DISCUSS] KIP-640 Add log compression analysis tool

decryption key somewhere measure the compression stats. > > On 2020/08/17 20:23:51, "Christopher Beard (BLOOMBERG/ 919 3RD A)" > wrote: > > Hi everyone, > > > > I would like to start a discussion on KIP-640: > > https://cwiki.apache.org/confluence/d

[DISCUSS] KIP-640 Add log compression analysis tool

Hi everyone, I would like to start a discussion on KIP-640: https://cwiki.apache.org/confluence/display/KAFKA/KIP-640%3A+Add+log+compression+analysis+tool This KIP outlines a new CLI tool which helps compare how the various compression types supported by Kafka reduce the size of a log (and there

Permission to propose a KIP

Hello, I'd like to propose a new KIP! My jira username is "cbeard". Thanks!

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

't necessarily be a producer involved? Yep, exactly :) Cheers, Chris On Thu, May 14, 2020 at 4:34 PM Christopher Egerton wrote: > Hi Randall, > > I think I prefer the method originally specified in the KIP. A separate > method can come with a contract about if/when it's called

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

Hi Randall, I think I prefer the method originally specified in the KIP. A separate method can come with a contract about if/when it's called so that tasks can assume that it's only invoked once over their lifetime, and allows connector developers to separate the logic for storing (and possibly do

Re: [DISCUSS] KIP-587 Suppress detailed responses for handled exceptions in security-sensitive environments

sted > in removing stack traces from all responses, which will expand the scope of > this KIP a bit. I'm going to update the wiki entry, and then would it be > reasonable to call for a vote? > > Thanks! > Connor > > On 4/17/20, 3:53 PM, "Christopher Egerton" wr

Re: [DISCUSS] KIP-611: Improved Handling of Abandoned Connectors and Tasks

change the calculus > in the second rejected alternative about keeping both the task- and > connector-based timeout property? I actually think it might. > 8. How much value does the sequence number in the logging context bring? Is > this really worth the risk given the backward

[DISCUSS] KIP-611: Improved Handling of Abandoned Connectors and Tasks

Hi all, I've introduced a KIP to improve how the Connect framework handles abandoned connectors and tasks: https://cwiki.apache.org/confluence/display/KAFKA/KIP-611%3A+Improved+Handling+of+Abandoned+Connectors+and+Tasks The improvements currently being proposed include new JMX metrics, a slight s

Re: [Discuss] KIP-582 Add a "continue" option for Kafka Connect error handling

tten learning curve of consumer tools, but also enabling extern tools > for > analysis. > > Best, > Zihan > > On 2020/05/03 17:36:34, Christopher Egerton wrote: > > Hi Zihan, > > > > I guess I'm still unclear on exactly what form this analysis might take. &

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

Hi Aakash, Thanks for the KIP! Given the myriad of different error-handling mechanisms available in sink connectors today, I think it'd be a great improvement to add this kind of support to the framework and not only take some of the development burden off of connector writers but also some of the

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

LGTM, +1 (non-binding) Thanks Randall! On Thu, May 7, 2020 at 11:01 AM Randall Hauch wrote: > I'd like to open the vote for KIP-605: > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-605%3A+Expand+Connect+Worker+Internal+Topic+Settings > > This is relatively straightforward, and the dis

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

lternative describing why I think failing is not desirable. > > 4. Added a sentence as suggested. > > Thanks! > > On Sun, May 3, 2020 at 12:55 PM Christopher Egerton > wrote: > > > Hi Randall, > > > > Thanks for the KIP! I have a few questions and suggestions b

Re: [VOTE] KIP-597: MirrorMaker2 internal topics Formatters

+1 (non-binding) On Mon, May 4, 2020 at 5:02 AM Edoardo Comar wrote: > +1 (non-binding) > Thanks Mickael > > -- > > Edoardo Comar > > Event Streams for IBM Cloud > IBM UK Ltd, Hursley Park, SO21 2JN > > > > > From: Mickael Maison > To: dev

Re: [DISCUSS] KIP-585: Conditional SMT

ivably implement on their own, and that the KIP > > introduces the > > > most likely ones as supplied implementations, much as there > are SMT > > > implementations such as HoistField. I don't really see users > > implementing > >

Re: [Discuss] KIP-581: Value of optional null field which has default value

only implement the > serialization now. This is because the original serde implement is not > symmetrical, the convertToConnect is a static method and can’t access the > field in JsonConverter > instance, maybe I should do some refactoring to implement the > deserialization. > >

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

Hi Randall, Thanks for the KIP! I have a few questions and suggestions but no major objections. 1. The motivation is pretty clear for altering the various "*.storage.replication.factor" properties to allow -1 as a value now. Are there expected use cases for allowing modification of other properti

Re: [Discuss] KIP-582 Add a "continue" option for Kafka Connect error handling

Task.putBrokenRecord() instead of DLQ. > > Best, > Zihan > > On 2020/04/25 20:05:37, Christopher Egerton wrote: > > Hi Zihan, > > > > Thanks for the changes and the clarifications! I agree that the > complexity > > of maintaining a second topic and a second

Re: [DISCUSS] KIP-597: MirrorMaker2 internal topics Formatters

ark it as > deprecated and make it extend the new interface. I've updated to the > KIP. > > > I've also opened a draft PR: https://github.com/apache/kafka/pull/8604 > > On Fri, Apr 24, 2020 at 12:17 AM Christopher Egerton > wrote: > > > > Hi Mickael,

Re: [DISCUSS] KIP-585: Conditional SMT

n FALSE if the predicate matches. > > I feel that a DSL for SMTs is overkill. If you need something that > complex, it's > perhaps too complex for a transformation chain and it's really a streaming > application. > > Andrew Schofield > IBM Event Streams > >

Re: [Discuss] KIP-582 Add a "continue" option for Kafka Connect error handling

to the KIP. Compared with this alternative, the point of this > proposal is to save the effort to maintain twice as many connectors as > necessary. > > Thanks again. Looking forward to the discussion! > > Sorry if you see this email twice, the previous one didn't sh

Re: [DISCUSS] KIP-597: MirrorMaker2 internal topics Formatters

Hi Mickael, The KIP looks great and the additional formatters seem like excellent tools for debugging and diving into the internals of Mirror Maker 2.0. I've got a few thoughts on the proposed changes: 1. Would it be possible to provide examples for what the actual output might look like when the

Re: [DISCUSS] KIP-587 Suppress detailed responses for handled exceptions in security-sensitive environments

cussion! > > > > RE: the 200 response you highlighted, great catch! I'll work with my > > customer and get back to you on their audit team's intention! I'm > > fairly certain I know the answer, but I need to be sure before I > speak >

Re: [Discuss] KIP-581: Value of optional null field which has default value

Hi Cheng, Thanks for the KIP! I really appreciate the care that was taken to ensure backwards compatibility for existing users, and the minimal changes to public interface that are suggested to address this. I have two quick requests for clarification: 1) Where is the proposed "accept.optional.n

Re: [Discuss] KIP-582 Add a "continue" option for Kafka Connect error handling

HI Zihan, Thanks for the KIP! I have some questions that I'm hoping we can address to help better understand the motivation for this proposal. 1. In the "Motivation" section it's written that "If users want to store their broken records, they have to config a broken record queue, which is too muc

Re: [DISCUSS] KIP-587 Suppress detailed responses for handled exceptions in security-sensitive environments

r. > > > > > > 3. I agree with your suggestion here. Absolutely ready to take > the > > > community feedback on what makes sense here. > > > > > > 4. I should note that while I emphasized uncau

Re: [DISCUSS] KIP-585: Conditional SMT

t;>> > >>> Would love to see this feature in one or another way in Connect. > >>> > >>> Best, > >>> > >>> --Gunnar > >>> > >>> > >>> > >>> Am Do., 2. Apr. 2020 um 18:48 Uhr

Re: [DISCUSS] KIP-587 Suppress detailed responses for handled exceptions in security-sensitive environments

Hi Connor, Great stuff! I generally like being able to see the stack trace of an exception directly via the REST API but can definitely understand the security concerns here. I've got a few questions/remarks about the KIP and would be interested in your thoughts: 1. The KIP mentions a SUPRESSED_E

Re: [DISCUSS] KIP-585: Conditional SMT

Hi Tom, This looks great and I'd love to see the out-of-the-box SMTs become even more powerful with the improvements you've proposed! Got a few remarks and would be interested in your thoughts: 1. Instead of the new "ConfigDef config(Map props)" method, what would you think about adopting a simil

Re: Working on a contribution for suppressing exceptions from KafkaConnect

Hi Connor, Thanks for the contribution! It looks like the feature you've implemented changes public interface, which means that a KIP would be required in order to merge them into Kafka. You can find more information about what kinds of changes require KIPs, what a KIP should consist of, and the p

Re: [VOTE] 2.5.0 RC2

uded in the next RC > > -David > > On Thu, Mar 26, 2020 at 6:01 PM Christopher Egerton > wrote: > > > Hi all, > > > > I'd like to request that > https://issues.apache.org/jira/browse/KAFKA-9771 > > be > > treated as a release blocker for 2

Re: [VOTE] 2.5.0 RC2

Hi all, I'd like to request that https://issues.apache.org/jira/browse/KAFKA-9771 be treated as a release blocker for 2.5. This is a regression caused by the recent bump in Jetty version that causes inter-worker communication to fail for Connect clusters that use SSL and a keystore that contains

Re: [DISCUSS] KIP-494 Connect REST Endpoint for Transformations (SMTs) and other Plugins

Hi Cyrus, Thanks for the KIP! One quick question--I see the use case for being able to list per-connector plugins (SMTs, converters, and header converters) via REST API, but I'm not so sure about worker plugins (REST extensions and config providers). Since those are configured at startup for the

Re: [DISCUSS] KIP-558: Track the set of actively used topics by connectors in Kafka Connect

lue for the newly-proposed parameter be? If resets are performed by default, the first scenario I outlined would become possible; if not, then the second would become possible. I'd lean towards performing them by default but would be interested in others' thoughts. (If the proposed &qu

Re: [DISCUSS] KIP-558: Track the set of actively used topics by connectors in Kafka Connect

Hi Konstantine, Thanks for the KIP! There's been a lot of productive discussion so far so I'll try to keep my remarks brief. 1. As far as resetting the active topics for a connector goes, it's noted in the KIP that this can be done for a deleted connector. Can this also be done for connectors tha

Re: OAuth Library - Open Source Contribution to Kafka

Christopher X Bogan has sent you an email via Gmail confidential mode: [image: Gmail logo]Re: OAuth Library - Open Source Contribution to Kafka <https://confidential-mail.google.com/msg/ABTZP1zFo7rxdar9IPiYuQi9Z2iJ9WYyy_8hctzuV8Xutn1i

Re: [VOTE] 2.4.0 RC2

Hi all, I'd like to submit https://issues.apache.org/jira/browse/KAFKA-9258 for blocker consideration. This issue affects the Connect framework and causes a 500 error to be thrown from the REST API when restarting a task that has failed during startup, even after the connector has been reconfigure

Re: Using Kafka Internals from Within Plugin

ectly seems a bit risky to me. > > > I'd love to hear what your authentication workflow looks like where you > need to actually read data from disk. > > On Fri, Mar 8, 2019 at 1:20 PM Christopher Vollick > wrote: > >> Hello! I'm experimenting with an implementa

Using Kafka Internals from Within Plugin

Hello! I'm experimenting with an implementation of AuthenticateCallbackHandler in an external JAR I’m loading, and I'd like to use some of the methods / properties from ReplicaManager (or KafkaServer which has a ReplicaManager), but I don't see anything that's passed to me or any singletons that

Re: Contribution

Hello I'm a little confused about the information how do I get added On Mon, Feb 11, 2019, 7:13 AM Kartik Kalaghatgi < karthikkalaghatgi...@gmail.com wrote: > Check out : > https://cwiki.apache.org/confluence/display/KAFKA/Contributing+Code+Changes > > -Kartik > > On Mon, 11 Feb 2019 at 5:00 PM,

[jira] [Resolved] (KAFKA-7874) NPE thrown while instantiating a KafkaStreams. object

[ https://issues.apache.org/jira/browse/KAFKA-7874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher S Lester resolved KAFKA-7874. - Resolution: Not A Bug auto commit interval was nil, resolving as not a bug

[jira] [Created] (KAFKA-7874) NPE thrown while instantiating a KafkaStreams. object

Christopher S Lester created KAFKA-7874: --- Summary: NPE thrown while instantiating a KafkaStreams. object Key: KAFKA-7874 URL: https://issues.apache.org/jira/browse/KAFKA-7874 Project: Kafka

Re: [DISCUSS] KIP-419 Safely notify Kafka Connect SourceTask is stopped

On 2019/01/18 18:02:24, Andrew Schofield wrote: > Hi,> > > I’ve created a new KIP to enhance the SourceTask interface in Kafka Connect.> > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-419:+Safely+notify+Kafka+Connect+SourceTask+is+stopped> > > > > Comments welcome.> > > > > Andrew S

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

On Fri, Dec 7, 2018 at 12:29 PM Ismael Juma wrote: > > Hi Daniel, > > We moved to Gitbox a while back for kafka and kafka-site. Which repository is > still using git-wip-us.apache.org? > > Ismael None of yours. The message was sent to every PMC. I believe https://git1-us-west.apache.org/repos/as

Semi Proposal: Unclean Leadership Elections and Out of Sync Brokers

Hey! I’m seeing behaviour I didn’t expect, and I’d like some expert opinions on it. (TL;DR min.insync.replicas=2 and acks=all isn’t enough to tolerate losing a leader transparently and safely, but maybe it could be) Lets say we have a topic with one partition, replication factor 3. Leader 0, Fo

Re: [DISCUSS] URIs on Producer and Consumer

I think this would be useful as a secondary way to configure. If others agree then you can write up a KIP and it can be discussed in more detail. On Tue, Oct 3, 2017 at 8:56 AM, Clebert Suconic wrote: > Maybe I didn't make the message clear enough... > > Would using an URI to the constructor (i

Re: [DISCUSS] KIP-127: Pluggable JAAS LoginModule configuration for SSL

of the SSLSession for my purposes. So I went ahead and closed out the JIRA and moved my KIP to the discarded section now that I verified it will work. Thanks again for the help. Chris On Fri, Feb 24, 2017 at 1:54 PM, Christopher Shannon < christopher.l.shan...@gmail.com> wrote: > So

[jira] [Resolved] (KAFKA-4784) Pluggable JAAS LoginModule configuration for SSL (KIP-127)

[ https://issues.apache.org/jira/browse/KAFKA-4784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher L. Shannon resolved KAFKA-4784. --- Resolution: Won't Fix Per feedback, a custom PrincipalBuilder c

Re: [DISCUSS] KIP-127: Pluggable JAAS LoginModule configuration for SSL

Sounds good, thanks for the feedback. I will move my KIP to the discarded section for now as the PrincipalBuilder should be sufficient. If for some reason it is not I can revisit this. Chris On Fri, Feb 24, 2017 at 1:37 PM Ismael Juma wrote: > Hi Christopher, > > It is possible to

Re: [DISCUSS] KIP-127: Pluggable JAAS LoginModule configuration for SSL

be good to let the user configure that regardless (i can do the jira/pr) On Fri, Feb 24, 2017 at 9:47 AM, Ismael Juma wrote: > Hi Christopher, > > Thanks for the KIP. I have two comments: > > 1. Can you please explain in the KIP (maybe in the Rejected Alternatives > section) w

  1   2   >