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
es 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 ultimately up to your judgement.
>
> Thanks,
> Greg
>
> On Mon, Apr 1,
ava/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 compatible with
> > Connect 4.0, or otherwise change t
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
of is that ConnectRestExtensions will need to be migrated,
> > > rebuilt, and re-released for 4.0+
> > >
> > > Can you explain how KIP-1013 and the Java version are relevant?
> > > Connect is dependent on this namespace, but will still need to support
> > >
er, and use the intervening time to properly notify downstream
> users to upgrade their Java versions.
>
> Thanks,
> Greg
>
> On Tue, Mar 26, 2024 at 9:04 AM Christopher Shannon
> wrote:
> >
> > Hi Greg,
> >
> > You are right that KIP-1013 and the
for 4.0+
>
> Can you explain how KIP-1013 and the Java version are relevant?
> Connect is dependent on this namespace, but will still need to support
> Java 11 in 4.0.
>
> Thanks!
> Greg
>
> On Tue, Mar 26, 2024 at 5:04 AM Christopher Shannon
> wrote:
> >
>
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
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
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
+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
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 <
> chri
"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. I cre
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
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
on 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
> >>>> написал(а):
> >>>&g
+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:
>
>
>
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
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
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
>
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
> CreateTopicPolicy a
since it's the recommended way to create topics.
>
> Ismael
>
> On Tue, Jun 8, 2021, 11:09 AM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > Hi Everyone,
> >
> > I'd like to propose KIP-755: Add new AUTO_CREATE ACL for auto
Shannon <
christopher.l.shan...@gmail.com> wrote:
> 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 KI
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 KIP ca
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:
; 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 Shannon
>
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
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
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
s long as the default remains that SSL client auth is disabled for
> SASL_SSL (which I believe is the common case), seems fine to me.
>
> Ismael
>
> On Fri, Feb 24, 2017 at 6:18 PM, Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > Rajini, If th
not achieve this via
> two separate listeners? username/password could be via a listener
> configured to use SASL and certificate-based could be via a listener
> configured to use TLS.
>
> Ismael
>
> On Tue, Feb 21, 2017 at 8:23 PM, Christopher Shannon <
> christopher.l
Does anyone else have any comments or suggestions on this?
On Tue, Feb 21, 2017 at 4:05 PM, Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> I should mention another reason I went with adding this enhancement to the
> SSL channel instead of SASL_SSL is that as you can
the handshake being completed so this would require
some refactoring to get to this to work properly and load at the right time.
On Tue, Feb 21, 2017 at 3:44 PM, Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:
> As a follow up to my previous post, EXTERNAL could be added to
can go either way on this, I can update my KIP to allow X509
authentication with SASL_SSL through the EXTERNAL mechanism or keep the
proposal as is for the SSL channel based on what everyone thinks.
On Tue, Feb 21, 2017 at 3:23 PM, Christopher Shannon <
christopher.l.shan...@gmail.com>
do so via SSL.
> I think we are providing too many options of authentication in SASL_SSL
> mode and can be bit confusing.
>
> Thanks,
> Harsha
>
>
> On Tue, Feb 21, 2017 at 11:23 AM Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> Hi everyone
>
Hi everyone
I have just created KIP-127 to introduce custom JAAS configuration for the
SSL channel:
*https://cwiki.apache.org/confluence/display/KAFKA/KIP-127%3A+Pluggable+JAAS+LoginModule+configuration+for+SSL
Awesome, thanks.
On Fri, Feb 17, 2017 at 2:30 PM, Guozhang Wang <wangg...@gmail.com> wrote:
> Done.
>
> Guozhang
>
> On Fri, Feb 17, 2017 at 10:20 AM, Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
> > Hi,
> >
> > I would li
Hi,
I would like to contribute a KIP. Can someone give me access to the wiki
to create pages?
Thanks,
Chris
38 matches
Mail list logo