+1 (binding) on the updated KIP.
Thanks for the updates!
On Fri, Dec 20, 2024 at 2:28 AM Matthias J. Sax wrote:
>
> I think I did miss the train to vote originally, but I am
>
> +1 (binding)
>
> on the updated KIP.
>
>
> -Matthias
>
> On 12/18/24 12:47 AM, Bruno Cadonna wrote:
> > Hi,
> >
> > We
Thank you for the KIP. Overall, the proposal looks good to me.
I am adding some additional comments here:
1. What type of constraints do we want to add on static configuration? I am
assuming we should probably define some sane lower limit so that basic
replication (empty fetch requests) can still
Kirk True created KAFKA-18400:
-
Summary: Don't use when formatting dates in Java client
Key: KAFKA-18400
URL: https://issues.apache.org/jira/browse/KAFKA-18400
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-17615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TaiJuWu resolved KAFKA-17615.
-
Assignee: Mickael Maison (was: Colin McCabe)
Resolution: Fixed
> Remove KafkaServer references in
I am moving this KIP to "discarded" state, as there was no further activity.
On 3/8/24 7:02 PM, Matthias J. Sax wrote:
Igor,
I did drop the ball on this discussion. Sorry about this. Too many
things are happening at the same time.
Also I do not think that emitting multiple records from th
[
https://issues.apache.org/jira/browse/KAFKA-4437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-4437.
Resolution: Abandoned
> Incremental Batch Processing for Kafka Streams
> --
Moving this KIP into "discarded" state. While header support is still
limited, we should rather move a `Record` base API following the new
PAPI, and thus this KIP does not make any sense any longer from my POV.
On 3/21/22 1:13 PM, Jorge Esteban Quilcate Otoya wrote:
Hi all,
With the acceptanc
[
https://issues.apache.org/jira/browse/KAFKA-15299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-15299.
-
Resolution: Incomplete
Closing this ticket as "incomplete".
The KIP discussion did not
[
https://issues.apache.org/jira/browse/KAFKA-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-6953.
Resolution: Abandoned
> [Streams] Schedulable KTable as Graph source (for minimizing aggreg
Moving this very old KIP into "discarded" state.
On 10/9/20 4:03 AM, Javier Freire Riobo wrote:
I see. It's great hidden functionality and all you have to do is define a
good API and expose it. I think the easiest thing would be to expose a
first operator, and then add more operators if they are
[
https://issues.apache.org/jira/browse/KAFKA-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-10578.
-
Resolution: Abandoned
Closing this ticket. The KIP discussion did not lead to a resoluti
Thanks David for the detailed review. Appreciated.
I will try to answer your most important question: what is the problem I am
trying to solve here.
This KIP will surely resolve some technical problems. But that's not the
original purpose. I am trying to resolve a problem in Kafka's design.
T
Thanks for the review.
This is an interesting idea. Indeed this will significantly reduce the data
need to be copied. But this may need to take the TTL time to get the new
replica join the ISRs. Also we need to consider how to handle the partitions
that will only do purge by data size.
On 2 Jan
Mickael Maison created KAFKA-18399:
--
Summary: Remove ZooKeeper from KafkaApis
Key: KAFKA-18399
URL: https://issues.apache.org/jira/browse/KAFKA-18399
Project: Kafka
Issue Type: Sub-task
Lucas Brutschy created KAFKA-18398:
--
Summary: Log a warning if actual topic configs are inconsistent
with the required topic configs
Key: KAFKA-18398
URL: https://issues.apache.org/jira/browse/KAFKA-18398
Hey TaiJu
I read the latest version of the KIP.
I understand the problem you are trying to solve here. But the solution
needs more changes than you proposed and hence, is not straightforward. As
an example, we haven't answered the question about protocol for
ProduceRequest raised above. A `Produc
[
https://issues.apache.org/jira/browse/KAFKA-17946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lucas Brutschy resolved KAFKA-17946.
Resolution: Fixed
> Flaky test DeafultStateUpdaterTest::shouldResumeStandbyTask due to
>
Hello Chen
Thank you for the KIP.
I have a few questions/thoughts:
1. Why can’t we achieve the objective without making any change at all? For
example, you can designate a few brokers as your “canary brokers” where
your custom "canary partitions" are situated. During rolling deployment you
can c
[
https://issues.apache.org/jira/browse/KAFKA-18256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swikar Patel resolved KAFKA-18256.
--
Resolution: Done
> Performance Testing (Optional but Recommended)
> --
[
https://issues.apache.org/jira/browse/KAFKA-18257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swikar Patel resolved KAFKA-18257.
--
Resolution: Done
> Update Documentation
>
>
> Key: KAFKA-
[
https://issues.apache.org/jira/browse/KAFKA-18258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swikar Patel resolved KAFKA-18258.
--
Resolution: Done
> Code Review
> ---
>
> Key: KAFKA-18258
>
21 matches
Mail list logo
