Senthilnathan Muthusamy created KAFKA-10642:
---
Summary: Expose the real stack trace if any exception occurred
during SSL Client Trust Verification in extension
Key: KAFKA-10642
URL: https
Senthilnathan Muthusamy created KAFKA-10641:
---
Summary: ACL Command hands with SSL as not existing with proper
error code
Key: KAFKA-10641
URL: https://issues.apache.org/jira/browse/KAFKA-10641
c08d79f3d1a8e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637152957096095910sdata=WE2SeBn2c%2BAce2YgAwfjvCvsYdZS8r8sSNZewZFFEUA%3Dreserved=0
to be interesting and helpful, too.
Ron
On Wed, Jan 22, 2020 at 2:07 AM Senthilnathan Muthusamy
wrote:
>
> Hi,
>
> We want both SASL (oAuthBearer) & SSL authenti
Hi,
We want both SASL (oAuthBearer) & SSL authentication to be enabled. However
based on the below doc, the SSL auth will be disabled if SASL is enabled.
https://docs.confluent.io/current/kafka/authentication_ssl.html#brokers
If any SASL authentication mechanisms are enabled for a given
og-compact topics with such
fragmented payloads.
On Tue, Nov 26, 2019 at 10:24 PM Senthilnathan Muthusamy
wrote:
>
> Thanks Jun for confirming!
>
> I have updated the KIP (added recommendation section and special case in
> handling LEO record for non-offset based compaction strategy).
on it again.
Thanks for driving the KIP discussion, and please feel free to ping the
community when the PR is ready for reviews! :) One minor recommendation is to
break it into smaller PRs to help on faster reviews and code merges.
Guozhang
On Tue, Nov 26, 2019 at 10:24 PM Senthilnathan Muthusamy
Jun
On Tue, Nov 26, 2019 at 10:24 PM Senthilnathan Muthusamy
wrote:
> Jun,
>
> If the updated KIP looks good, can you please vote for it.
>
> Thanks,
> Senthil
>
> -Original Message-
> From: Jun Rao
> Sent: Thursday, November 7, 2019 4:33 PM
> To: dev
&g
to preserve the
log end offset.
53. Yes, your understanding is correct. So we could recommend users to set "
max.compaction.lag.ms" properly if they care about deletes.
Could you add both to the KIP?
Thanks,
Jun
On Tue, Nov 26, 2019 at 5:09 AM Senthilnathan Muthusamy
wrote:
> Hi G
on the discussion thread.
Jun
On Wed, Nov 6, 2019 at 3:38 AM Senthilnathan Muthusamy
wrote:
> Thanks Matthias!
>
> Received 2 +1 binding... looking for one more +1 binding !
>
> Regards,
> Senthil
>
> -Original Message-
> From: Matthias J. Sax
> Sent: Wednes
Hi Gouzhang & Jun,
Can one of you please confirm/respond to the below mail so that I will go ahead
and update the KIP and proceed.
Thanks
Senthil
- Senthil
From: Senthilnathan Muthusamy
Sent: Wednesday, November 20, 2019 5:04:20 PM
To: dev@kafka.apache
th smaller timestamp / headers may not be
compacted correctly since the tombstone is already gone and hence we do not
have the "proof" to remove it anymore.
Does that make sense to you?
Guozhang
On Tue, Nov 12, 2019 at 9:15 AM Senthilnathan Muthusamy
wrote:
> Hi Jun,
>
> T
:37 AM Senthilnathan Muthusamy
wrote:
> Hi Guozhang,
>
> Sure and I have made a note in the JIRA item to make sure the wiki is
> updated.
>
> Thanks,
> Senthil
>
> -Original Message-
> From: Guozhang Wang
> Sent: Monday, November 4, 2019 11:00 AM
> T
:44 AM, Senthilnathan Muthusamy wrote:
> Thanks Gouzhang and I have made a note in the JIRA item to update the wiki.
>
> Till now got 1 +1 binding... waiting for 2 more +1 binding... thnx!
>
> Regards,
> Senthil
>
> -Original Message-
> From: Guozhang Wang
>
: Enhanced log compaction
I only have one minor comment on the DISCUSS thread, otherwise I'm +1 (binding).
On Mon, Nov 4, 2019 at 9:53 AM Senthilnathan Muthusamy
wrote:
> Hi all,
>
> I would like to start the vote on the updated KIP-280: Enhanced log
> compaction. Thanks to Guozhang, Ma
ng
On Mon, Nov 4, 2019 at 9:52 AM Senthilnathan Muthusamy
wrote:
> Hi all,
>
> I will start the vote thread shortly for this updated KIP. If there
> are any more thoughts I would love to hear them.
>
> Thanks,
> Senthil
>
> -Original Message-
> From: S
; > wiki otherwise LGTM.
> >
> > 1. We should emphasize that the newly introduced config yields to
> > the existing "log.cleanup.policy", i.e. if the latter's value is
> > `delete` not `compact`, then the previous config would be ignored.
> >
> >
&
Hi all,
I would like to start the vote on the updated KIP-280: Enhanced log compaction.
Thanks to Guozhang, Matthias & Tom for the valuable feedback on the discussion
thread...
KIP:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-280%3A+Enhanced+log+compaction
JIRA:
Hi all,
I will start the vote thread shortly for this updated KIP. If there are any
more thoughts I would love to hear them.
Thanks,
Senthil
-Original Message-
From: Senthilnathan Muthusamy
Sent: Thursday, October 31, 2019 3:51 AM
To: dev@kafka.apache.org
Subject: RE: [DISCUSS] KIP
that solves all issue for interleaved writes,
but I personally believe, it's a good improvement.
-Matthias
On 10/30/19 9:45 AM, Senthilnathan Muthusamy wrote:
> Hi,
>
> Please let me know if anyone has any questions on this updated KIP-280...
>
> Thanks,
>
> Senthil
&g
Hi,
Please let me know if anyone has any questions on this updated KIP-280...
Thanks,
Senthil
-Original Message-
From: Senthilnathan Muthusamy
Sent: Monday, October 28, 2019 11:36 PM
To: dev@kafka.apache.org
Subject: RE: [DISCUSS] KIP-280: Enhanced log compaction
Hi Tom,
Sorry
Tom
On Mon, Oct 21, 2019 at 9:06 PM Senthilnathan Muthusamy
wrote:
> Hi All,
>
> We are bring back the KIP-280 to live with small correct for the
> discussion & voting. Thanks to previous author Luis Cabral on the
> KIP-280 initiation and we are taking over to compl
Hi All,
We are bring back the KIP-280 to live with small correct for the discussion &
voting. Thanks to previous author Luis Cabral on the KIP-280 initiation and we
are taking over to complete and get it into 2.4...
Below is the correction that we made to the existing KIP-280:
* Allowing
22 matches
Mail list logo
