Hi Vicky,
I checked the KIP again, and found there's something you might need to have
some description.
The term: *scan query*, is my first time seeing this term.
I think it's not a publicly known term (or it's just me?), and might need
some description for it.
And for the "range query", I think
Hi Patrick,
Thanks for the KIP!
I have some comments, in addition to Guozhang's comments:
4. The parameter names `windowLower` and `windowUpper` are kind of
ambiguous to me. Could we come up a better name for it, like
`windowStartTime`, `windowEndTime`, or even we don't need the "window"
name,
Bumping this thread another time.
This is a very minor change to make DescribeLogDirsResponse consistent
with the other APIs.
Let me know if you have any feedback.
Thanks,
Mickael
On Mon, Nov 22, 2021 at 10:29 AM Tom Bentley wrote:
>
> Hi Mickael,
>
> It's pretty low value, but I think
Hi all,
I'd like to start a vote on KIP-769 which proposes adding new
endpoints to the Connect REST API to list all connectors plugins and
retrieve their configurations.
nk2242696 created KAFKA-13540:
-
Summary: UniformStickyPartitioner leads to uneven Kafka partitions
Key: KAFKA-13540
URL: https://issues.apache.org/jira/browse/KAFKA-13540
Project: Kafka
Issue
Patrick Stuedi created KAFKA-13541:
--
Summary: Make IQv2 query/store interface type safe
Key: KAFKA-13541
URL: https://issues.apache.org/jira/browse/KAFKA-13541
Project: Kafka
Issue Type:
Rajini Sivaram created KAFKA-13539:
--
Summary: Improve propagation and processing of SSL handshake
failures
Key: KAFKA-13539
URL: https://issues.apache.org/jira/browse/KAFKA-13539
Project: Kafka
Hello everyone,
Thank you for your comments. I applied the changes.
Hope things are clearer now.
Best,
Vicky
On Mon, Dec 13, 2021 at 8:24 AM Luke Chen wrote:
> Hi Vicky,
>
> I checked the KIP again, and found there's something you might need to have
> some description.
> The term: *scan
Thanks Mickael, this looks great. +1 non-binding.
Cheers,
Chris
On Mon, Dec 13, 2021 at 5:18 AM Mickael Maison
wrote:
> Hi all,
>
> I'd like to start a vote on KIP-769 which proposes adding new
> endpoints to the Connect REST API to list all connectors plugins and
> retrieve their
Hi David,
It looks good, I just noticed a typo:
"KIP-733" should be "KIP-773"
Thanks
On Sun, Dec 12, 2021 at 4:05 PM David Jacot wrote:
>
> Hi Luke,
>
> Thanks for your feedback. I have found and have fixed the issue. It was
> actually
> due to the formatting of the title of the AK 3.0 blog
Hello everyone,
Thank you for the discussion and for voting.
The vote on KIP-805 passes with: 3 binding +1 (John, Matthias, and
Guozhang), 1 non-binding +1 (Luke), no vetoes.
The vote is now closed.
If anyone has objections later on, please don't hesitate to let me know.
I will proceed with
Hi kafka-devs,
I would like a second review to the proposed changes on KIP-795: Add public
APIs for AbstractCoordinator
[
https://cwiki.apache.org/confluence/display/KAFKA/KIP-795%3A+Add+public+APIs+for
+AbstractCoordinator ]
I've amended the KIP addressing Tom's feedback, and also opened a
Hi, Lucas,
Thanks for the reply. It would be useful to summarize the benefits of a
separate batch.max.size. To me, it's not clear why a user would want two
different batch sizes. In your example, I can understand why a user would
want to form a batch with a 5ms linger. But why would a user prefer
Hi Jun,
On Thu, Dec 9, 2021, at 2:28 PM, Jun Rao wrote:
> 13. Using OpenTelemetry. Does that require runtime dependency
> on OpenTelemetry library? How good is the compatibility story
> of OpenTelemetry? This is important since an application could have other
> OpenTelemetry dependencies than the
Hi all,
I'd like to start the vote on KIP-801: Implement an Authorizer that stores
metadata in __cluster_metadata
The KIP is here: https://cwiki.apache.org/confluence/x/h5KqCw
The original DISCUSS thread is here:
https://lists.apache.org/thread/3d5o7h17ztjztjhblx4fln0wbbs1rmdq
Please take a
A. Sophie Blee-Goldman created KAFKA-13542:
--
Summary: Utilize the new Consumer#enforceRebalance(reason) API in
Streams
Key: KAFKA-13542
URL: https://issues.apache.org/jira/browse/KAFKA-13542
Hi John,
Please see my follow-up comments inlined below.
On Mon, Dec 13, 2021 at 2:26 PM John Roesler wrote:
> Hi Patrick, thanks for the KIP!
>
> I hope you, Guozhang, and Luke don't mind if I share some
> thoughts:
>
> 1. I think you just meant to remove that private constructor
> from the
Hi José,
I think these are good questions. We have a few situations like this where
there is something brokers have to know before they can contact the controller
quorum -- or something controllers have to know before they can accept broker
connections. Basically, the bootstrapping problem.
A. Sophie Blee-Goldman created KAFKA-13543:
--
Summary: Consumer may pass stale cluster metadata to the assignor
following a subscription update
Key: KAFKA-13543
URL:
Hi Igor,
Disk failures have always required manual intervention in Kafka. For example,
if you are using a RAID array and a disk goes bad, you will need to remove the
disk, insert a new one, and start the RAID rebuild process. Kafka can't help
with this process since we don't operate at this
Hi Patrick, thanks for the KIP!
I hope you, Guozhang, and Luke don't mind if I share some
thoughts:
1. I think you just meant to remove that private constructor
from the KIP, right?
2. I think WindowRangeQuery#withWindowRage(windowLower,
windowUpper) is the version that yields an iterator over
I think we should be very careful about introducing new runtime
dependencies into the clients. Historically this has been rare and
essentially necessary (e.g. compression libs).
Ryanne
On Mon, Dec 13, 2021, 1:06 PM Kirk True wrote:
> Hi Jun,
>
> On Thu, Dec 9, 2021, at 2:28 PM, Jun Rao wrote:
+1 (non-binding)
Ryanne
On Mon, Dec 13, 2021, 4:18 AM Mickael Maison
wrote:
> Hi all,
>
> I'd like to start a vote on KIP-769 which proposes adding new
> endpoints to the Connect REST API to list all connectors plugins and
> retrieve their configurations.
>
>
Hi David,
I think we should get https://issues.apache.org/jira/browse/KAFKA-13488.
This is a follow-up to https://issues.apache.org/jira/browse/KAFKA-12257,
which was previously considered a 3.0 blocker. Without the additional
patch, the bug causing the consumer to get stuck can still occur in a
[
https://issues.apache.org/jira/browse/KAFKA-13540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Livshits resolved KAFKA-13540.
Resolution: Duplicate
See also
25 matches
Mail list logo
