hold back a Scala 3 release of Kafka-Streams-Scala. I
> would appreciate some guidance as to what the release process should look
> like in the future.
>
> Oh and I've made a PR to remove a syntax error from release.py.
> https://github.com/apache/kafka/pull/15350
>
>
[
https://issues.apache.org/jira/browse/KAFKA-14975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew de Detrich resolved KAFKA-14975.
Resolution: Won't Fix
Closing issue since the core problem was solved in an
standing, high-impact issues.
>
> He has also been an active participant in discussions and reviews on the
> mailing lists and on GitHub.
>
> Thanks for all of your contributions, Greg. Congratulations!
>
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße
Matthew de Detrich created KAFKA-14975:
--
Summary: Make TopicBasedRemoteLogMetadataManager methods wait for
initialize to complete
Key: KAFKA-14975
URL: https://issues.apache.org/jira/browse/KAFKA-14975
Matthew de Detrich created KAFKA-14332:
--
Summary: Split out checkstyle configs between test and main
Key: KAFKA-14332
URL: https://issues.apache.org/jira/browse/KAFKA-14332
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew de Detrich resolved KAFKA-14283.
Resolution: Fixed
> Fix connector creation authorization tests not doing anyth
Matthew de Detrich created KAFKA-14283:
--
Summary: Fix connector creation authorization tests not doing
anything
Key: KAFKA-14283
URL: https://issues.apache.org/jira/browse/KAFKA-14283
Project
Matthew de Detrich created KAFKA-14256:
--
Summary: Update to Scala 2.13.9
Key: KAFKA-14256
URL: https://issues.apache.org/jira/browse/KAFKA-14256
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-14223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew de Detrich resolved KAFKA-14223.
Resolution: Invalid
Created in wrong project
> Update jdk_17_latest to adopt
Matthew de Detrich created KAFKA-14223:
--
Summary: Update jdk_17_latest to adoptium 17.0.4+1
Key: KAFKA-14223
URL: https://issues.apache.org/jira/browse/KAFKA-14223
Project: Kafka
Issue
Matthew de Detrich created KAFKA-14221:
--
Summary: Update Apache Kafka JVM version in CI to latest versions
Key: KAFKA-14221
URL: https://issues.apache.org/jira/browse/KAFKA-14221
Project: Kafka
Matthew de Detrich created KAFKA-14103:
--
Summary: Check for hostnames in CoreUtils.scala
Key: KAFKA-14103
URL: https://issues.apache.org/jira/browse/KAFKA-14103
Project: Kafka
Issue
Matthew de Detrich created KAFKA-13980:
--
Summary: Update to Scala 2.12.16
Key: KAFKA-13980
URL: https://issues.apache.org/jira/browse/KAFKA-13980
Project: Kafka
Issue Type: Improvement
Luke Chen wrote:
> >
> > Hi Matthew,
> >
> > Thanks for the update.
> > I'm +1 (binding)
> >
> > Thank you.
> > Luke
> >
> > On Fri, Feb 11, 2022 at 3:32 PM Matthew de Detrich
> > wrote:
> >
> > > Hi Luke,
> >
th IPv4
> and IPv6 on the same port.
> And some examples to show how the validation will fail like you listed in
> `Proposed Changes`.
>
> Thank you.
> Luke
>
>
> On Fri, Feb 11, 2022 at 8:54 AM Matthew de Detrich
> wrote:
>
> > Hello everyone
> >
> &
Hello everyone
I have just updated/rebased the PR against the latest Kafka trunk. Let me
know if anything else is required/missing.
Regards
On Thu, Jan 13, 2022 at 10:28 AM Matthew de Detrich <
matthew.dedetr...@aiven.io> wrote:
> Does anyone have any additional comments/regards to
the KIP.
> > > It makes sense to allow IPv4 and IPv6 listening on the same port for
> the
> > > listener config.
> > >
> > > +1 (non-binding)
> > >
> > > Thank you.
> > > Luke
> > >
> > > On Mon, Nov 22, 2021 at 6:2
de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
*m:* +491603708037
*w:* aiven.io *e:* matthew.dedetr...@aiven.io
t; We stated: Listener names and port numbers must be unique.
> It'll be wrong after this KIP.
>
> Also, the PR link should not be put onto the KIP. You can put in the JIRA
> comment.
>
> Thank you.
> Luke
>
> On Thu, Nov 18, 2021 at 7:34 PM Matthew de Detrich
>
n that your change only apply to "listeners", not "advertised
> listeners".
>
> Also, you should also mention in the KIP, that the doc for "listeners" will
> also be updated. (I checked your PR, and found you missed that)
>
> Thank you.
> Luke
>
> On
Since no one has commented on either this thread or the original one I will
summon a vote by the end of this week.
Regards
On Wed, Nov 10, 2021 at 5:28 PM Matthew de Detrich <
matthew.dedetr...@aiven.io> wrote:
> Hello everyone,
>
> I would like to start a discussion for KIP-797
?pageId=195726330
Regards
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
*m:* +491603708037
*w:* aiven.io *e:* matthew.dedetr...@aiven.io
proposal, since it is a change to
> our public interfaces. Also, there are some subtle questions that we need
> to answer, like do the ipv4 and ipv6 interfaces that share the same port
> also have to share the same security protocol?
>
> best,
> Colin
>
>
> On Fri, Sep 24
> also have to share the same security protocol?
>
> best,
> Colin
>
>
> On Fri, Sep 24, 2021, at 01:44, Matthew de Detrich wrote:
> > Hello everyone,
> >
> > I wanted to ask if anyone has any thoughts/objections regarding Kafka
> > allowing multiple list
nd IPv6 on the same port, does anyone have comments on this?
Relevant Ticket: https://issues.apache.org/jira/browse/KAFKA-13299
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa &
Matthew de Detrich created KAFKA-13299:
--
Summary: Accept listeners that have the same port but use IPv4 vs
IPv6
Key: KAFKA-13299
URL: https://issues.apache.org/jira/browse/KAFKA-13299
Project
Hello everyone,
Does anyone know what the contact email is for Kafka PMC? I have a couple
of questions regarding the Kafka trademark (i.e.
https://www.apache.org/foundation/marks/faq/#poweredby and
https://kafka.apache.org/trademark)
Regards
--
Matthew de Detrich
*Aiven Deutschland GmbH
it can?
> >
> > I think the current behavior is reasonable, esp considering precedent
> from
> > Connect and Streams, both of which actively create topics as needed.
> >
> > But I understand the motivation. Have they considered revoking topic
> > creation
ting issue on this at
https://issues.apache.org/jira/browse/KAFKA-12753
@Ryanne @Mickael Since you guys are the main developers on MM/MM2 what are
your thoughts on this?
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HR
configs, etc. The only Scala API that is public facing is the
> Kafka Streams Scala API. Is this KIP focused on that?
>
> Ismael
>
> On Tue, Jun 8, 2021 at 3:29 AM Matthew de Detrich
> wrote:
>
> > Hello everyone,
> >
> > I'd like to discuss the followin
Pull request has been made at https://github.com/apache/kafka/pull/10839
On Tue, Jun 8, 2021 at 12:28 PM Matthew de Detrich <
matthew.dedetr...@aiven.io> wrote:
> Hello everyone,
>
> I'd like to discuss the following KIP which involves making all scala case
> class's
to
source breaking change.
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
*m:* +491603708037
*w:* aiven.io *e:* matthew.dedetr...@aiven.io
Matthew de Detrich created KAFKA-12913:
--
Summary: Make Scala Case class's final
Key: KAFKA-12913
URL: https://issues.apache.org/jira/browse/KAFKA-12913
Project: Kafka
Issue
t; >
> > > > > > Since the goal is to provide ample warning regarding the future
> > > removal
> > > > > of
> > > > > > Scala 2.12 and the change we're proposing for 3.0 is simply a
> > > > > documentation
> >
497
> > > > > >
> > > > > > w: aiven.io
> > > > > >
> > > > > > e: josep.p...@aiven.io
> > > > > >
> > > > > > On Mon, Jun 7, 2021, 15:51 Ismael Juma
> wrote:
> > > > &
echnically speaking you do need to create one however
because of what I just said it may not be needed?
Regards
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
*m:*
later today and hopefully
> can
> > start reviewing it soon in a few days.
> >
> > Viktor
> >
> > On Tue, May 18, 2021 at 11:50 AM Matthew de Detrich
> > wrote:
> >
> >> Forgot to mention the code that was never merged in the PR
> >>
>
nternal
> thread pool, but the primary motivation here, at least for me, is to fix
> the lie the API is telling, not to improve performance.
>
> Ryanne
>
>
>
> On Wed, May 26, 2021, 6:51 AM Matthew de Detrich
> wrote:
>
> > I think we may need to clarify terminol
; > waiting" part of KIP-739 to add your suggestion as my recommended
> approach,
> > thank you! If no one else has major concerns about that approach, I'll
> > move the alternatives to "rejected alternatives".
> >
> > On Thu, May 20, 2021 at 7:26 A
credit all authors. Just make sure it's clearly stated in
> the PR, so the committer is aware of it.
>
>
> https://docs.github.com/en/github/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors
>
> On Fri, May 21, 2021 at 10:00 A
ntityReplicationPolicy (which seems to be the general consensus) or
> LegacyReplicationPolicy (which is what I called it back in KIP-382). I'm
> onboard with IdentityReplicationPolicy, but this [Discuss] thread is a good
> place to bring it up in case anyone objects.
>
> Ryanne
>
need for a KIP.
On Wed, May 19, 2021 at 11:12 AM Matthew de Detrich <
matthew.dedetr...@aiven.io> wrote:
> Hey Ryanne,
>
> Thanks for the reply, personally I have a slight preference for my
> implementation since it doesn't require the "cheating" with the
>
Matthew de Detrich created KAFKA-12819:
--
Summary: Quality of life improvements for tests
Key: KAFKA-12819
URL: https://issues.apache.org/jira/browse/KAFKA-12819
Project: Kafka
Issue
of users to override specific threadpools for
exceptional cases (i.e. providing a Threadpool that is pinned to a single
core which tends to give the best latency results if this is something that
is critical for you).
My suggestion was just do this in multiple steps/phases, firstly let's fix
t
cally translated
to gitter. Furthermore Gitter also has other advantages, such as automatic
archival of messages (you do not need to be online or use a cloud/server to
maintain messages if you are offline).
Let me know what are your thoughts.
--
Matthew de Detrich
*Aiven Deutschland
> > > understand) if we're targeting the "user provides the
> thread"
> > > > > approach.
> > > > > > > > >
> > > > > > > > > From looking at the code, I think we can keep record
> > > > serializa
nus
> remote.topic.suffix) and your tests and get to a working state without any
> changes to the public interface, wdyt?
>
> Ryanne
>
> On Mon, May 10, 2021 at 6:02 PM Matthew de Detrich
> wrote:
>
> > Hello everyone.
> >
> > I have a KIP that involv
Hello,
I would like to start contributing to Apache Kafka, could you add my
username (mdedetrich-aiven) to the contributors list for the Apache Kafka
project?
Regards
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
Forgot to mention the code that was never merged in the PR
https://github.com/omkreddy/kafka/commit/fc47aa8d06828ef1de1c12b6c33192e10e3afd0c
On Tue, May 18, 2021 at 11:42 AM Matthew de Detrich <
matthew.dedetr...@aiven.io> wrote:
> Apologies for necro/bump on this topic, but I am
and if so would there
be any issues if I was to go forward in rebasing commit for latest trunk and
creating a new PR for it?
--
Matthew de Detrich
Aiven Deutschland GmbH
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
m: +491603708037
w: aiven.io e
works. There is already a passing PR open with the
implementation at https://github.com/apache/kafka/pull/10648
Happy to receive votes and/or feedback on the proposal.
Regards
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB
t any
breaking changes.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-737%3A+Add+canTrackSource+to+ReplicationPolicy
Cheers
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
*m:* +491603708037
*w:* aiven.
Wiki Id: mdedetrich-aiven
--
Matthew de Detrich
*Aiven Deutschland GmbH*
Immanuelkirchstraße 26, 10405 Berlin
Amtsgericht Charlottenburg, HRB 209739 B
*m:* +491603708037
*w:* aiven.io *e:* matthew.dedetr...@aiven.io
53 matches
Mail list logo
