+1
Best,
Mattison
On Tue, 3 May 2022 at 22:38, Andras Beni
wrote:
> Hi Enrico,
>
> I updated the proposal with my answers:
>
> [The translation from user-visible name to actual storage path] will
> happen by supplying the bucket number to
> TopicName.getPersistenceNamingEncoding and calculatin
Hi Enrico,
I updated the proposal with my answers:
[The translation from user-visible name to actual storage path] will
happen by supplying the bucket number to
TopicName.getPersistenceNamingEncoding and calculating the modified path.
Since the bottleneck is listing topics, which happens using t
How do we deal with Schema storage, Cursors and other usages of
ManagedLedger?
Can you please clarify each case I'm which we use ManagedLedger?
Did you try to put up a proff or concept with this proposal?
I generally agree with this approach but it looks like we are not going
deep enough in the
+1
Thanks,
Hang
PengHui Li 于2022年4月25日周一 09:20写道:
>
> +1
>
> Penghui
>
> On Thu, Apr 21, 2022 at 9:17 PM Andras Beni
> wrote:
>
> > Hi everyone,
> >
> > I've just created a proposal that will help scaling up the number of topics
> > per namespace.
> > It's available at https://github.com/apache
+1
Penghui
On Thu, Apr 21, 2022 at 9:17 PM Andras Beni
wrote:
> Hi everyone,
>
> I've just created a proposal that will help scaling up the number of topics
> per namespace.
> It's available at https://github.com/apache/pulsar/issues/15254 and is
> copied below.
> Let me know what you think.
>
Hi everyone,
I've just created a proposal that will help scaling up the number of topics
per namespace.
It's available at https://github.com/apache/pulsar/issues/15254 and is
copied below.
Let me know what you think.
Thanks,
Andras
Motivation
Pulsar is able to manage millions of topics but the