Hi all,
In case someone missed the first message in this thread, it can be read at
https://lists.apache.org/thread/tvco1orf0hsyt59pjtfbwoq0vf6hfrcj .
The intention is to start discussions about improving Apache Pulsar design
in Pulsar 3.0 . This seems to be the first time that we are discussing
Hi, Lari
Thanks for you start this discussion.
1) Metadata consistency from user's point of view
> - Summarized well in this great analysis and comment [1] by Zac Bentley
>"Ideally, the resolution of all of these issues would be the same: a
> management API operation--any operation--should
It is a huge milestone, but a challenge for implementing pluggable metadata
storage. Will the plan go from providing pluggable metadata storage to
internalize the distributed coordination functionality of Pulsar itself
finally?
Lari Hotari 于2022年8月16日周二 11:17写道：
> Bumping up this thread.
>
>
Bumping up this thread.
-Lari
pe 20. toukok. 2022 klo 1.57 Lari Hotari kirjoitti:
> Hi all,
>
> I started writing this email as feedback to "PIP-157: Bucketing topic
> metadata to allow more topics per namespace" [3].
> This email expanded to cover some analysis of "PIP-45: Pluggable metadata
Hi all,
I started writing this email as feedback to "PIP-157: Bucketing topic
metadata to allow more topics per namespace" [3].
This email expanded to cover some analysis of "PIP-45: Pluggable metadata
interface" [4] design. (A good introduction to PIP-45 is the StreamNative
blog post "Moving
