checking the code here, I think we throw
> > StreamsException when they are found not defined during runtime, we
> > actually throw the `*ConfigException*`. So for consistency we could just
> > use that exception as well.
> >
> > Guozhang
> >
> >
Just a friendly ping to please check out the finalized proposal of the KIP
and (re)cast your votes
Thanks!
Sophie
On Sun, May 16, 2021 at 7:28 PM Sophie Blee-Goldman
wrote:
> Thanks John. I have moved the discussion over to a [DISCUSS] thread, where
> it should have been taking pla
ey Leah,
> > >
> > > > what I think should be a small discussion
> > >
> > > Dangerous words, indeed! It seems like they trigger something in people
> > ;-)
> > >
> > > Jokes apart!
> > >
> > > Did you consid
[
https://issues.apache.org/jira/browse/KAFKA-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-9295.
---
Resolution: Fixed
> KTableKTableForeignKeyInnerJoinMultiIntegrationT
fy our policy.
However this was ultimately rejected for other reasons, see the KIP.
Thanks all,
Sophie
On Sun, May 16, 2021 at 11:40 PM Sophie Blee-Goldman
wrote:
> Changing `TaskId` to an abstract class and deprecate all util functions /
>> fields that we do not
>> want to expose a
>
> what I think should be a small discussion
Dangerous words :P
I'm all for the proposal but I do have one question about something in the
KIP. You list two methods called
defaultKeySerde() and defaultValueSerde() but it's not clear to me where
these are coming from. Are they
new APIs you
stract class and deprecate all util functions / fields that we do not
> want to expose any longer, and 3) introducing a new class that extends the
> o.a.k.streams.processor.TaskId for internal implementations?
>
>
> Guozhang
>
>
> On Sun, May 16, 2021 at 7:19 PM Soph
ta, right?
> Why not just add those methods to TaskMetadata? Stepping
> back, the concept of metadata about an identifier is a bit
> elaborate.
>
> Sorry for thrashing what you were hoping would be a quick,
> uncontroversial KIP.
>
> Thanks for your consideration,
> John
ple above to "TaskInfo". Or we could
take a similar approach and just build on the original TaskId name, calling
it TaskIdInfo or something like that. Any thoughts? As always the KIP has
been updated with what I am proposing, so you can take a look yourself.
On Sun, May 16, 2021 at 7:
I'm moving the discussion on KIP-740 to an actual [DISCUSS] thread since it
turned out to be more nuanced
and grew in scope since I initially proposed it. Thanks John for
the suggestions/questions on the [VOTE] thread,
I have copied them over and addressed them below.
Before that, I just want to
[
https://issues.apache.org/jira/browse/KAFKA-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12754.
Fix Version/s: 3.0.0
Resolution: Fixed
> TaskMetadata endOffs
class, and public TaskIdMetadata interface,
where appropriate.
On Thu, May 13, 2021 at 6:42 PM Sophie Blee-Goldman
wrote:
> Thanks all. I updated the KIP slightly since there is some ambiguity
> around whether the existing TaskId class is
> currently part of the public API or not.
A. Sophie Blee-Goldman created KAFKA-12782:
--
Summary: Javadocs search sends you to a non-existent URL
Key: KAFKA-12782
URL: https://issues.apache.org/jira/browse/KAFKA-12782
Project: Kafka
n-binding)
> >
> > Walker
> >
> > On Thu, May 13, 2021 at 1:53 PM Sophie Blee-Goldman
> > wrote:
> >
> > > Hey all,
> > >
> > > I'm just going to take this KIP straight to a vote since it should be a
> > > trivial and unco
[
https://issues.apache.org/jira/browse/KAFKA-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-8326.
---
Fix Version/s: 3.0.0
Resolution: Fixed
> Add Serde> s
[
https://issues.apache.org/jira/browse/KAFKA-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman reopened KAFKA-9295:
---
Unfortunately it seems to still be failing :/
[https://ci-builds.apache.org
Hey all,
I'm just going to take this KIP straight to a vote since it should be a
trivial and uncontroversial change. Of course please raise any concerns
should they come up, and I can take things to a DISCUSS thread.
The KIP is a simple change to move from String to TaskId for the taskID
field
A. Sophie Blee-Goldman created KAFKA-12779:
--
Summary: Use TaskId instead of String for the taskId field in
TaskMetadata
Key: KAFKA-12779
URL: https://issues.apache.org/jira/browse/KAFKA-12779
Hey Vipul,
There's no "rebalance.protocol" config, as the protocol is determined by
the supported partition
assignors. The assignors can be configured with the config
"partition.assignment.strategy". I
suspect the "rebalance.protocol" comment was a leftover from an older
version of the proposal.
A. Sophie Blee-Goldman created KAFKA-12748:
--
Summary: Explore new RocksDB options to consider enabling by
default
Key: KAFKA-12748
URL: https://issues.apache.org/jira/browse/KAFKA-12748
A. Sophie Blee-Goldman created KAFKA-12747:
--
Summary: Flaky Test
RocksDBStoreTest.shouldReturnUUIDsWithStringPrefix
Key: KAFKA-12747
URL: https://issues.apache.org/jira/browse/KAFKA-12747
A. Sophie Blee-Goldman created KAFKA-12746:
--
Summary: Allow StreamThreads to recover from some exceptions
without killing/replacing the thread
Key: KAFKA-12746
URL: https://issues.apache.org/jira/browse
A. Sophie Blee-Goldman created KAFKA-12742:
--
Summary: 5. Checkpoint all uncorrupted state stores within the
subtopology
Key: KAFKA-12742
URL: https://issues.apache.org/jira/browse/KAFKA-12742
A. Sophie Blee-Goldman created KAFKA-12741:
--
Summary: 4. Handle thread-wide errors
Key: KAFKA-12741
URL: https://issues.apache.org/jira/browse/KAFKA-12741
Project: Kafka
Issue Type
A. Sophie Blee-Goldman created KAFKA-12740:
--
Summary: 3. Resume processing from last-cleared processor after
soft crash
Key: KAFKA-12740
URL: https://issues.apache.org/jira/browse/KAFKA-12740
A. Sophie Blee-Goldman created KAFKA-12739:
--
Summary: 2. Commit any cleanly-processed records within a
corrupted task
Key: KAFKA-12739
URL: https://issues.apache.org/jira/browse/KAFKA-12739
A. Sophie Blee-Goldman created KAFKA-12738:
--
Summary: Improved error handling for better at-least-once
semantics and faster EOS
Key: KAFKA-12738
URL: https://issues.apache.org/jira/browse/KAFKA-12738
A. Sophie Blee-Goldman created KAFKA-12737:
--
Summary: Commit all healthy tasks after a task-specific error for
better task isolation and reduced overcounting under ALOS
Key: KAFKA-12737
URL: https
[
https://issues.apache.org/jira/browse/KAFKA-6409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-6409.
---
Resolution: Duplicate
> LogRecoveryT
[
https://issues.apache.org/jira/browse/KAFKA-6655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-6655.
---
Resolution: Fixed
This should be fixed, a number of improvements were made
ve been:
> >
> > public static *SessionWindows *ofInactivityGapAndGrace(final Duration
> > inactivityGap, final Duration afterWindowEnd);
> >
> > I will update the KIP to reflect what I think it needs to be. Please let
> > me know your thoughts when you see t
Thanks for the KIP, +1 (binding)
-Sophie
On Wed, Apr 28, 2021 at 10:46 AM Jason Gustafson
wrote:
> Hi All,
>
> I'd like to start a vote on KIP-735:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-735%3A+Increase+default+consumer+session+timeout
> .
> +1
> from myself obviously
>
>
[
https://issues.apache.org/jira/browse/KAFKA-9295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman reopened KAFKA-9295:
---
Still failing, saw this on both the Java 8 and Java 11 build of a PR
A. Sophie Blee-Goldman created KAFKA-12727:
--
Summary: Flaky test
ListConsumerGroupTest.testListConsumerGroupsWithStates
Key: KAFKA-12727
URL: https://issues.apache.org/jira/browse/KAFKA-12727
[
https://issues.apache.org/jira/browse/KAFKA-12666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12666.
Resolution: Duplicate
> Fix fl
A. Sophie Blee-Goldman created KAFKA-12721:
--
Summary: Flaky Test
ResetConsumerGroupOffsetTest.testResetOffsetsAllTopicsAllGroups
Key: KAFKA-12721
URL: https://issues.apache.org/jira/browse/KAFKA-12721
[
https://issues.apache.org/jira/browse/KAFKA-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-6435.
---
Resolution: Fixed
> Application Reset Tool might delete incorrect inter
[
https://issues.apache.org/jira/browse/KAFKA-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12344.
Fix Version/s: 3.0.0
Resolution: Fixed
> Support SlidingWind
t this config explicitly when deploying new applications in
> such clusters.
>
> If so, I'm fine with the KIP, but I think we should update it to cover the
> points above (some may already be covered).
>
> Ismael
>
> On Tue, Apr 20, 2021 at 12:59 PM Sophie Blee-Goldman
> w
re if we will need a new vote for these so please let me know!
>
> Thanks!
> Sagar.
>
> On Sun, Apr 4, 2021 at 7:55 AM Sophie Blee-Goldman
> wrote:
>
> > I think you can start the vote, we can always return to the discussion if
> > someone raises a
> > concern dur
Hey Jason,
Thanks for the KIP, I think increasing the default session timeout would be
great. The choice of
45s sounds reasonable to me.
-Sophie
On Fri, Apr 23, 2021 at 9:29 AM Jason Gustafson
wrote:
> Hi All,
>
> I've created a KIP to change the default consumer session timeout as well
> as
A. Sophie Blee-Goldman created KAFKA-12710:
--
Summary: Consider enabling (at least some) optimizations by default
Key: KAFKA-12710
URL: https://issues.apache.org/jira/browse/KAFKA-12710
A. Sophie Blee-Goldman created KAFKA-12706:
--
Summary: Consider adding reason and source of error in
APPLICATION_SHUTDOWN
Key: KAFKA-12706
URL: https://issues.apache.org/jira/browse/KAFKA-12706
, and Zalando, among others.
A big thank you for the following 26 contributors to this release!
A. Sophie Blee-Goldman, Andy Wilkinson, Bob Barrett, Bruno Cadonna,
Chia-Ping Tsai, Chris Egerton, dengziming, Greg Harris, Ismael Juma, Jim
Galasyn, John Roesler, Julien Jean Paul Sirocchi, Lee Dongjin
A. Sophie Blee-Goldman created KAFKA-12700:
--
Summary: The admin.listeners config has wonky valid values in the
docs
Key: KAFKA-12700
URL: https://issues.apache.org/jira/browse/KAFKA-12700
amendment to my previous vote tally, Tom should have been
listed under
the Committers column
On Mon, Apr 19, 2021 at 10:13 AM Sophie Blee-Goldman
wrote:
> This vote passes with 5 +1 votes (3 bindings) and no 0 or -1 votes.
>
> +1 votes
> PMC Members:
> * Guozhang Wang
> * Joh
FWIW if someone is deploying a new Streams application to production and
they don't
set this config, either because they are not reading the docs or they just
forgot, then imo
it's actually better for them to hit this exception and fail-fast if the
brokers don't support it.
Currently, the default
Apr 15, 2021 at 2:43 PM Guozhang Wang
> > wrote:
> > >
> > >> +1 as well (binding). Thanks Sophie!
> > >>
> > >> On Thu, Apr 15, 2021 at 7:29 AM Bruno Cadonna
> > wrote:
> > >>
> > >>> Sophie,
> > >>>
A. Sophie Blee-Goldman created KAFKA-12690:
--
Summary: Remove deprecated Producer#sendOffsetsToTransaction
Key: KAFKA-12690
URL: https://issues.apache.org/jira/browse/KAFKA-12690
Project
A. Sophie Blee-Goldman created KAFKA-12689:
--
Summary: Remove deprecated EOS configs
Key: KAFKA-12689
URL: https://issues.apache.org/jira/browse/KAFKA-12689
Project: Kafka
Issue Type
This vote passes with 5 +1 votes (3 bindings) and no 0 or -1 votes.
+1 votes
PMC Members:
* Guozhang Wang
* John Roesler
* Bill Bejeck
Committers:
* Myself (Sophie Blee-Goldman)
Community:
* Tom Bentley
0 votes
* No votes
-1 votes
* No votes
Vote
thread:https://lists.apache.org/thread.html
::onPartitionsLost to avoid unnecessary task failures
> > on
> > > consumer protocol downgrade, but besides that, I don't think things
> could
> > > get any smoother for Connect users or developers. The automatic
> protocol
> > > upgrade/downgrade behavior appe
Hey all,
I'd like to kick off the vote on KIP-732, to deprecate eos-alpha in Kafka
Streams and migrate away from the "eos-beta" terminology by replacing it
with "eos-v2" to shore up user confidence in this feature.
upport for alpha/v1 altogether
> > then why not remove all that too?
> >
> > From: Sophie Blee-Goldman
> > Sent: Wednesday, April 14, 2021 5:22 PM
> > To: dev
> > Subject: Re: [DISCUSS] KIP-732: Deprecate eos-alpha and rep
Thanks Matthias. I'm +1 (binding)
-Sophie
On Wed, Apr 14, 2021 at 3:36 PM Matthias J. Sax wrote:
> Hi,
>
> Because this KIP is rather small, I would like to skip a dedicated
> discussion thread and call for a vote right way. If there are any
> concerns, we can just discuss on this vote thread:
data(consumerGroupId));
}
On Wed, Apr 14, 2021 at 2:19 PM Matthias J. Sax wrote:
> I don't think we should deprecate the producer method, because there are
> also "producer only" application that may use this method.
>
> For example, source connectors.
>
>
> -Matthia
d parameter?
>
> This would encourage non-Streams EOS users to move to beta/v2
> implementations, and the fallback to alpha/v1 mode code can also be removed
> in 4.0.
> ________
> From: Sophie Blee-Goldman
> Sent: Wednesday, April 14, 2021 4:38 PM
> T
arer about the removal plans? That is, can we say that the
> > deprecated
> > > > configs will be removed in 4.0 (instead of likely to be removed)? The
> > > > implication would be that exactly-once would only work with 2.5+
> while
> > at
> > > > le
[
https://issues.apache.org/jira/browse/KAFKA-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12667.
Resolution: Fixed
> Incorrect error log on StateDirectory cl
Hey all,
I'd like to kick off discussion on a small KIP to move towards a unified
EOS and clean up the current options. Please give it a pass and let me know
what you think.
KIP-732: Deprecate eos-alpha and replace eos-beta with eos-v2
[
https://issues.apache.org/jira/browse/KAFKA-12637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12637.
Resolution: Fixed
> Remove deprecated PartitionAssignor interf
[
https://issues.apache.org/jira/browse/KAFKA-8391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman reopened KAFKA-8391:
---
[~rhauch] [~kkonstantine] this test failed again -- based on the error message
[
https://issues.apache.org/jira/browse/KAFKA-12284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman reopened KAFKA-12284:
Assignee: (was: Luke Chen)
Failed again, on both the SSL and plain
A. Sophie Blee-Goldman created KAFKA-12650:
--
Summary: NPE in InternalTopicManager#cleanUpCreatedTopics
Key: KAFKA-12650
URL: https://issues.apache.org/jira/browse/KAFKA-12650
Project: Kafka
A. Sophie Blee-Goldman created KAFKA-12649:
--
Summary: Expose cache resizer for dynamic memory allocation
Key: KAFKA-12649
URL: https://issues.apache.org/jira/browse/KAFKA-12649
Project: Kafka
A. Sophie Blee-Goldman created KAFKA-12648:
--
Summary: Experiment with resilient isomorphic topologies
Key: KAFKA-12648
URL: https://issues.apache.org/jira/browse/KAFKA-12648
Project: Kafka
ct?
>
> Thank you very much for finding this great solution.
>
> Luke
>
> On Fri, Apr 9, 2021 at 11:37 AM Sophie Blee-Goldman
> wrote:
>
> > Alright, here's the detailed proposal for KAFKA-12477. This assumes we
> will
> > change the default assignor to [&qu
Hey all,
This KIP has been accepted with
four +1 (binding) votes from John, Guozhang, Matthias, and myself
four +1 (non-binding) votes from Leah, Walker, Lotz, and Israel
Thanks everyone. Israel will take it from here
On Thu, Apr 8, 2021 at 2:58 PM Sophie Blee-Goldman
wrote:
> > I woul
stead, we should
> > probably call that fact out in the KIP as well and state that Connect
> will
> > now override the default partition assignment strategy to be the range
> > assignor (assuming the user hasn't specified a value for
> > consumer.partition.assignment.
A. Sophie Blee-Goldman created KAFKA-12638:
--
Summary: Remove default implementation of
ConsumerRebalanceListener#onPartitionsLost
Key: KAFKA-12638
URL: https://issues.apache.org/jira/browse/KAFKA-12638
A. Sophie Blee-Goldman created KAFKA-12637:
--
Summary: Remove deprecated PartitionAssignor interface
Key: KAFKA-12637
URL: https://issues.apache.org/jira/browse/KAFKA-12637
Project: Kafka
Thomas
> >
> > >>> wrote:
> > >>>
> > >>>> Thanks for picking this up, Sophie. +1 from me, non-binding.
> > >>>>
> > >>>> Leah
> > >>>>
> > >>>>> On Mon, Apr 5, 20
m
> the
> > API names since it is a very important concept and hence worth
> emphasizing
> > to users up front.
> >
> > Guozhang
> >
> > On Wed, Mar 31, 2021 at 1:58 PM John Roesler
> wrote:
> >
> >> Thanks for bringing this up, Sophie!
&
Closing this vote, please refer to the [VOTE] 2.6.2 RC1 thread
On Wed, Mar 31, 2021 at 3:41 PM Justin Mclean wrote:
> Hi,
>
> > Can you clarify a few things?
>
> Sorry I'm not subscribed to this list and only just saw this.
>
> > - On the first point, the only thing I see is zstd, which we do
Hello Kafka users, developers and client-developers,
This is the second candidate for release of Apache Kafka 2.6.2.
Apache Kafka 2.6.2 is a bugfix release and fixes 35 issues since the 2.6.1
release. Please see the release notes for more information.
Release notes for the 2.6.2 release:
[
https://issues.apache.org/jira/browse/KAFKA-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12624.
Resolution: Fixed
> Fix LICENSE in
Congrats!
On Wed, Apr 7, 2021 at 6:32 PM Luke Chen wrote:
> Congrats Bruno!!
>
> Luke
>
> On Thu, Apr 8, 2021 at 9:18 AM Matthias J. Sax wrote:
>
> > Congrats Bruno! Very well deserved!
> >
> >
> > -Matthias
> >
> > On 4/7/21 3:51 PM, Bill Bejeck wrote:
> > > Congrats Bruno! Well deserved.
> >
[
https://issues.apache.org/jira/browse/KAFKA-8924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-8924.
---
Resolution: Duplicate
> Default grace period (-1) of TimeWindows cau
[
https://issues.apache.org/jira/browse/KAFKA-6603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-6603.
---
Resolution: Fixed
> Kafka streams off heap memory usage does not ma
[
https://issues.apache.org/jira/browse/KAFKA-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-8165.
---
Resolution: Fixed
> Streams task causes Out Of Memory after connect
Thanks for the KIP! +1 (binding) from me
Cheers,
Sophie
On Mon, Apr 5, 2021 at 7:13 PM Sagar wrote:
> Hi All,
>
> I would like to start voting on the following KIP:
>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=177047930
>
> Thanks!
> Sagar.
>
Hey all,
I'd like to start the voting on KIP-633, to drop the awkward 24 hour grace
period and improve the API to raise visibility on an important concept in
Kafka Streams: grace period nad out-of-order data handling.
Here's the KIP:
P or should
> we wait a bit longer?
>
> Thanks!
> Sagar.
>
> On Fri, Apr 2, 2021 at 11:59 PM Sophie Blee-Goldman
> wrote:
>
> > Yeah sure, window.inner.class.deserializer sounds good to me
> >
> > On Fri, Apr 2, 2021 at 11:28 AM Leah Thomas >
>
e feedback! I have updated the KIP inline with whatever
> > you
> > > > suggested.
> > > >
> > > > Regarding point 5, I have added the note as it makes sense to not set
> > the
> > > > config via the KafkaStreams app.
> > > >
> > &g
s sense to not set the
> config via the KafkaStreams app.
>
> Thanks!
> Sagar.
>
>
> On Wed, Mar 24, 2021 at 7:52 AM Sophie Blee-Goldman
> wrote:
>
> > Hey Sagar,
> >
> > Thanks for the KIP! The overall proposal looks good to me, but I had some
>
A. Sophie Blee-Goldman created KAFKA-12595:
--
Summary: New Consumer metric for records/bytes committed
Key: KAFKA-12595
URL: https://issues.apache.org/jira/browse/KAFKA-12595
Project: Kafka
Hey all,
It's finally time to reconsider the default grace period in Kafka Streams,
and hopefully save a lot of suppression users from the pain of figuring out
why their results don't show up until 24 hours later. Please check out the
proposal and let me know what you think.
KIP:
gt; Kind regards
> Georg
>
> -----Original Message-
> From: Sophie Blee-Goldman
> Sent: Friday, March 19, 2021 11:44 PM
> To: Bruno Cadonna
> Cc: dev ; us...@kafka.apache.org;
> kafka-clie...@googlegroups.com
> Subject: Re: [kafka-clients] [VOTE] 2.6.2 RC0
>
>
[
https://issues.apache.org/jira/browse/KAFKA-9897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman reopened KAFKA-9897:
---
> Flaky Test StoreQueryIntegrationTest#shouldQuerySpecificActivePartitionSto
it
> > > comes to the brokers, they are often managed by a central group (or
> > they're
> > > in the Cloud), so they're a bit easier to manage. Even so, it's still
> > > possible to upgrade from 0.8.x directly to 2.7 since all protocol
> >
[
https://issues.apache.org/jira/browse/KAFKA-12509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12509.
Resolution: Fixed
> Tighten up StateDirectory thread lock
A. Sophie Blee-Goldman created KAFKA-12574:
--
Summary: Deprecate eos-alpha
Key: KAFKA-12574
URL: https://issues.apache.org/jira/browse/KAFKA-12574
Project: Kafka
Issue Type
Ismael,
It seems like given 3.0 is a breaking release, we have to rely on users
being aware of this and responsible
enough to read the upgrade guide. Otherwise we could never ever make any
breaking changes beyond just
removing deprecated APIs or other compilation-breaking errors that would be
A. Sophie Blee-Goldman created KAFKA-12569:
--
Summary: Clean up usage of commit flags in StateMachineTask
Key: KAFKA-12569
URL: https://issues.apache.org/jira/browse/KAFKA-12569
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-12537.
Fix Version/s: 2.8.0
Resolution: Fixed
> Single Threaded
Thanks for the KIP! I'm 100% on board with this (obviously :P) and the KIP
itself looks good to me
overall. Just one clarification I think you should make:
In the *Public Interfaces* section you say "It won't affect the current
consumers" -- this is only true
if those current consumers have
Just noticed you started up a new DISCUSS thread for this KIP with the
updated KIP
number -- I'll copy my response over to the latest thread.
On Fri, Mar 26, 2021 at 12:22 PM Sophie Blee-Goldman
wrote:
> Thanks for the KIP! I'm 100% on board with this (obviously :P) and the KIP
> itself
[
https://issues.apache.org/jira/browse/KAFKA-10396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
A. Sophie Blee-Goldman resolved KAFKA-10396.
Resolution: Fixed
> Overall memory of container keep on growing
Thanks for the KIP! I'm 100% on board with this (obviously :P) and the KIP
itself looks good to me
overall. Just one clarification I think you should make:
In the *Public Interfaces* section you say "It won't affect the current
consumers" -- this is only true
if those current consumers have
A. Sophie Blee-Goldman created KAFKA-12559:
--
Summary: Add a top-level Streams config for bounding off-heap
memory
Key: KAFKA-12559
URL: https://issues.apache.org/jira/browse/KAFKA-12559
301 - 400 of 809 matches
Mail list logo
