Re: [DISCUSS] Apache Kafka 2.6.0 release

[Mario Molina]

Hi Randal,

Ticket https://issues.apache.org/jira/browse/KAFKA-9018 is not a blocker so
it can be moved to the 2.7.0 version.

Mario

On Wed, 24 Jun 2020 at 20:22, Boyang Chen 
wrote:

> Hey Randal,
>
> There was another spotted blocker:
> https://issues.apache.org/jira/browse/KAFKA-10173
> As of current, John is working on a fix.
>
> Boyang
>
> On Wed, Jun 24, 2020 at 4:08 PM Sophie Blee-Goldman 
> wrote:
>
> > Hey all,
> >
> > Just a heads up that we discovered a new blocker. The fix is pretty
> > straightforward
> > and there's already a PR for it so it should be resolved quickly.
> >
> > Here's the ticket: https://issues.apache.org/jira/browse/KAFKA-10198
> >
> > On Sat, May 30, 2020 at 12:52 PM Randall Hauch  wrote:
> >
> > > Hi, Kowshik,
> > >
> > > Thanks for the update on KIP-584. This is listed on the "Postponed"
> > section
> > > of the AK 2.6.0 release plan (
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152113430
> > > ).
> > >
> > > Best regards,
> > >
> > > Randall
> > >
> > > On Fri, May 29, 2020 at 4:51 PM Kowshik Prakasam <
> kpraka...@confluent.io
> > >
> > > wrote:
> > >
> > > > Hi Randall,
> > > >
> > > > We have to remove KIP-584 from the release plan, as this item will
> not
> > be
> > > > completed for 2.6 release (although KIP is accepted). We plan to
> > include
> > > it
> > > > in a next release.
> > > >
> > > >
> > > > Cheers,
> > > > Kowshik
> > > >
> > > >
> > > > On Fri, May 29, 2020 at 11:43 AM Maulin Vasavada <
> > > > maulin.vasav...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Randall Hauch
> > > > >
> > > > > Can we add KIP-519 to 2.6? It was merged to Trunk already in April
> -
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=128650952
> > > > > .
> > > > >
> > > > > Thanks
> > > > > Maulin
> > > > >
> > > > > On Fri, May 29, 2020 at 11:01 AM Randall Hauch 
> > > wrote:
> > > > >
> > > > > > Here's an update on the AK 2.6.0 release.
> > > > > >
> > > > > > Code freeze was Wednesday, and the release plan [1] has been
> > updated
> > > to
> > > > > > reflect all of the KIPs that made the release. We've also cut the
> > > `2.6`
> > > > > > branch that we'll use for the release; see separate email
> > announcing
> > > > the
> > > > > > new branch.
> > > > > >
> > > > > > The next important date for the 2.6.0 release is CODE FREEZE on
> > JUNE
> > > > 10,
> > > > > > and until that date all bug fixes are still welcome on the
> release
> > > > > branch.
> > > > > > But after that, only blocker bugs can be merged to the release
> > > branch.
> > > > > >
> > > > > > If you have any questions or concerns, please contact me or
> (better
> > > > yet)
> > > > > > reply to this thread.
> > > > > >
> > > > > > Thanks, and best regards!
> > > > > >
> > > > > > Randall
> > > > > >
> > > > > > [1] AK 2.6.0 Release Plan:
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152113430
> > > > > >
> > > > > >
> > > > > > On Wed, May 27, 2020 at 5:53 PM Matthias J. Sax <
> mj...@apache.org>
> > > > > wrote:
> > > > > >
> > > > > > > Thanks Randall!
> > > > > > >
> > > > > > > I added missing KIP-594.
> > > > > > >
> > > > > > >
> > > > > > > For the postponed KIP section: I removed KIP-441 and KIP-444 as
> > > both
> > > > > are
> > > > > > > completed.
> > > > > > >
> > > > > > >
> > > > > > > -Matthias
> > > > > > >
> > > > > > > On 5/27/20 2:31 PM, Randall Hauch wrote:
> > > > > > > > Hey everyone, just a quick update on the 2.6.0 release.
> > > > > > > >
> > > > > > > > Based on the release plan (
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152113430
> > > > > > > ),
> > > > > > > > today (May 27) is feature freeze. Any major feature work that
> > is
> > > > not
> > > > > > > > already complete will need to push out to the next release
> > > (either
> > > > > 2.7
> > > > > > or
> > > > > > > > 3.0). There are a few PRs for KIPs that are nearing
> completion,
> > > and
> > > > > > we're
> > > > > > > > having some Jenkins build issues. I will send another email
> > later
> > > > > today
> > > > > > > or
> > > > > > > > early tomorrow with an update, and I plan to cut the release
> > > branch
> > > > > > > shortly
> > > > > > > > thereafter.
> > > > > > > >
> > > > > > > > I have also updated the list of planned KIPs on the release
> > plan
> > > > > page (
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=152113430
> > > > > > > ),
> > > > > > > > and I've moved to the "Postponed" table any KIP that looks
> like
> > > it
> > > > is
> > > > > > not
> > > > > > > > going to be complete today. If any KIP is in the wrong table,
> > > > please
> > > > > > let
> > > > > > > me
> > > > > > > > know.
> > > > > > > >
> > > > > > > > If you have any questions or concerns, please feel free to

[jira] [Created] (KAFKA-9985) Sink connector may exhaust broker when writing in DLQ

[Mario Molina (Jira)]

Mario Molina created KAFKA-9985:
---

 Summary: Sink connector may exhaust broker when writing in DLQ
 Key: KAFKA-9985
 URL: https://issues.apache.org/jira/browse/KAFKA-9985
 Project: Kafka
  Issue Type: Bug
Affects Versions: 2.4.1, 2.5.0, 2.3.1
Reporter: Mario Molina
Assignee: Mario Molina
 Fix For: 2.6.0


When a sink connector is configured with a DLQ and its topic is the same (or 
matches) as the topic in which the connector reads, the broker and/or connector 
might be exhausted in case the record send to the topic is invalid.

Based on the broker/connect config, the connector might fail throwing a 
RecordTooLargeException previous to exhaust the broker/connector.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

[Mario Molina]

Hi all,

I'd like to start a vote for KIP-586. You can find the link for this KIP
here:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-586%3A+Deprecate+commit+records+without+record+metadata

Thanks!
Mario

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

[Mario Molina]

Hi,

I've updated the comment in the KIP (even though it was already included in
the PR).

Thanks!
Mario

On Fri, 3 Apr 2020 at 09:01, Randall Hauch  wrote:

> Hi, Mario.
>
> Thanks for creating this small but useful KIP! The only suggestion I have
> is to include the JavaDoc for the method we want to deprecate so that we
> can include the line:
>
> * @deprecated Use {@link #commitRecord(SourceRecord, RecordMetadata)}
>
>
> This will make it more clear that there are two methods with the same name
> and we're deprecating only one of them.
>
> Best regards,
>
> Randall
>
> On Wed, Apr 1, 2020 at 8:07 PM Mario Molina  wrote:
>
> > Hi all,
> >
> > I'd like to use this thread to discuss KIP-586.
> > You can see the detail at:
> >
> >
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-586%3A+Deprecate+commit+records+without+record+metadata
> >
> > Best,
> > Mario
> >
>

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

[Mario Molina]

Hi all,

I'd like to use this thread to discuss KIP-586.
You can see the detail at:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-586%3A+Deprecate+commit+records+without+record+metadata

Best,
Mario

[jira] [Created] (KAFKA-9780) Deprecate commit records without record metadata

[Mario Molina (Jira)]

Mario Molina created KAFKA-9780:
---

 Summary: Deprecate commit records without record metadata
 Key: KAFKA-9780
 URL: https://issues.apache.org/jira/browse/KAFKA-9780
 Project: Kafka
  Issue Type: Improvement
  Components: KafkaConnect
Affects Versions: 2.4.1
Reporter: Mario Molina
Assignee: Mario Molina
 Fix For: 2.5.0, 2.6.0


Since KIP-382 (MirrorMaker 2.0) a new method {{commitRecord}} was included in 
{{SourceTask}} class to be called by the worker adding a new parameter with the 
record metadata. The old {{commitRecord}} method is called and from the new one 
and it's preserved just for backwards compatibility.

The idea is to deprecate this method so that we could remove it in a future 
release.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [DISCUSS] KIP-510: Metrics library upgrade

[Mario Molina]

Could we start the discussion?

On Wed, 21 Aug 2019 at 08:57, Mario Molina  wrote:

> Hi there,
>
> I've written KIP-510
> <https://cwiki.apache.org/confluence/display/KAFKA/KIP-510%3A+Metrics+library+upgrade>
> proposing the upgrade of the metrics library which Kafka is using.
>
> Please, have a look and let me know what you think,
> Thanks,
> Mario
>

[DISCUSS] KIP-510: Metrics library upgrade

[Mario Molina]

Hi there,

I've written KIP-510

proposing the upgrade of the metrics library which Kafka is using.

Please, have a look and let me know what you think,
Thanks,
Mario

Request permission

[Mario Molina]

Hi,

I'd like to create a new page for a KIP in the Apache Kafka Confluence site.
The implementation of this KIP is already done but changes some things in
the API that should be approved. You can check it out here
.

My ID in Confluence is "mmolimar".

Regards,
Mario

[jira] [Created] (KAFKA-8721) Metrics library upgrade

[Mario Molina (JIRA)]

Mario Molina created KAFKA-8721:
---

 Summary: Metrics library upgrade
 Key: KAFKA-8721
 URL: https://issues.apache.org/jira/browse/KAFKA-8721
 Project: Kafka
  Issue Type: Improvement
  Components: metrics
Affects Versions: 2.3.0
Reporter: Mario Molina


The current metrics library which Kafka is using is pretty old (version 2.2.0 
from Yammer and now we have 4.1.0 from Dropwizard).

In the latest versions of the Dropwizard library (which comes from Yammer and 
this is deprecated), there are a lot of bugfixes and new features included 
which could be interesting for the metrics (ie: Reservoris, support JDK9, etc).

This patch includes the upgrade to this new version of the library so that we 
could add new features in Kafka metrics.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Resolved] (KAFKA-6836) Upgrade metrics library

[Mario Molina (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-6836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mario Molina resolved KAFKA-6836.
-
Resolution: Won't Fix

> Upgrade metrics library
> ---
>
> Key: KAFKA-6836
> URL: https://issues.apache.org/jira/browse/KAFKA-6836
> Project: Kafka
>  Issue Type: Improvement
>  Components: metrics
>Affects Versions: 1.1.0
>Reporter: Mario Molina
>    Assignee: Mario Molina
>Priority: Major
>
> The current metrics library which Kafka is using is pretty old (version 2.2.0 
> from Yammer and now we have 4.X from Dropwizard).
> In the latest versions of the Dropwizard library (which comes from Yammer and 
> this is deprecated), there are a lot of bugfixes and new features included 
> which could be interesting for the metrics (ie: Reservoris, support JDK9, 
> etc).
> This patch includes the upgrade to this new version of the library so that we 
> could add new features in Kafka metrics.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (KAFKA-6836) Upgrade metrics library

[Mario Molina (JIRA)]

Mario Molina created KAFKA-6836:
---

 Summary: Upgrade metrics library
 Key: KAFKA-6836
 URL: https://issues.apache.org/jira/browse/KAFKA-6836
 Project: Kafka
  Issue Type: Improvement
  Components: metrics
Affects Versions: 1.1.0
Reporter: Mario Molina
Assignee: Mario Molina
 Fix For: 2.0.0, 1.1.1


The current metrics library which Kafka is using is pretty old (version 2.2.0 
from Yammer and now we have 4.X from Dropwizard).

In the latest versions of the Dropwizard library (which comes from Yammer and 
this is deprecated), there are a lot of bugfixes and new features included 
which could be interesting for the metrics (ie: Reservoris, support JDK9, etc).

This patch includes the upgrade to this new version of the library so that we 
could add new features in Kafka metrics.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (KAFKA-5975) No response when deleting topics and delete.topic.enable=false

[Mario Molina (JIRA)]

Mario Molina created KAFKA-5975:
---

 Summary: No response when deleting topics and 
delete.topic.enable=false
 Key: KAFKA-5975
 URL: https://issues.apache.org/jira/browse/KAFKA-5975
 Project: Kafka
  Issue Type: Bug
  Components: core
Affects Versions: 0.11.0.0
Reporter: Mario Molina
Priority: Minor
 Fix For: 0.11.0.1, 0.11.0.2


When trying to delete topics using the KafkaAdminClient and the flag in server 
config is set as 'delete.topic.enable=false', the client cannot get a response 
and fails returning a timeout error. This is due to the object 
DelayedCreatePartitions cannot complete the operation.

This bug fix modifies the KafkaApi key DELETE_TOPICS taking into account that 
the flag can be disabled and swallow the error to the client, this is, the 
topic is never removed and no error is returned to the client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KAFKA-5218) New Short serializer, deserializer, serde

[Mario Molina (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mario Molina updated KAFKA-5218:

External issue URL:   (was: https://github.com/apache/kafka/pull/3017)

> New Short serializer, deserializer, serde
> -
>
> Key: KAFKA-5218
> URL: https://issues.apache.org/jira/browse/KAFKA-5218
> Project: Kafka
>  Issue Type: Improvement
>  Components: clients
>Affects Versions: 0.10.1.1, 0.10.2.0
>Reporter: Mario Molina
>Priority: Minor
> Fix For: 0.11.0.0
>
>
> There is no Short serializer/deserializer in the current clients component.
> It could be useful when using Kafka-Connect to write data to databases with 
> SMALLINT fields (or similar) and avoiding conversions to int improving a bit 
> the performance in terms of memory and network.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (KAFKA-5218) New Short serializer, deserializer, serde

[Mario Molina (JIRA)]

 [ 
https://issues.apache.org/jira/browse/KAFKA-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mario Molina updated KAFKA-5218:

External issue URL: https://github.com/apache/kafka/pull/3017

> New Short serializer, deserializer, serde
> -
>
> Key: KAFKA-5218
> URL: https://issues.apache.org/jira/browse/KAFKA-5218
> Project: Kafka
>  Issue Type: Improvement
>  Components: clients
>Affects Versions: 0.10.1.1, 0.10.2.0
>Reporter: Mario Molina
>Priority: Minor
> Fix For: 0.11.0.0
>
>
> There is no Short serializer/deserializer in the current clients component.
> It could be useful when using Kafka-Connect to write data to databases with 
> SMALLINT fields (or similar) and avoiding conversions to int improving a bit 
> the performance in terms of memory and network.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (KAFKA-5218) New Short serializer, deserializer, serde

[Mario Molina (JIRA)]

Mario Molina created KAFKA-5218:
---

 Summary: New Short serializer, deserializer, serde
 Key: KAFKA-5218
 URL: https://issues.apache.org/jira/browse/KAFKA-5218
 Project: Kafka
  Issue Type: Improvement
  Components: clients
Affects Versions: 0.10.2.0, 0.10.1.1
Reporter: Mario Molina
Priority: Minor
 Fix For: 0.11.0.0


There is no Short serializer/deserializer in the current clients component.

It could be useful when using Kafka-Connect to write data to databases with 
SMALLINT fields (or similar) and avoiding conversions to int improving a bit 
the performance in terms of memory and network.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)