Thank you all,
Close the vote with 3 (+1) bindings, and 4 (+1) non-bindings.
I will continue the release process.
On Thu, 14 Jul 2022 at 13:05, Michael Marshall wrote:
> +1 (non-binding)
>
> - Verified signatures for all 48 artifacts
> - Verified sha512 checksums for all 48 artifacts
> - Verif
If we use per-tenant system topic or per-namespace. and there is no active
topic in the tenant anymore, how we consume the msg in this tenant.
This is the concern I cared about, so I prefer to use system topic.
On Thu, Jul 14, 2022 at 9:59 AM Asaf Mesika wrote:
> >
> > No, as it's mentioned in PIP: this API will terminate the topic so, it
> will
> > not allow any new write and producers on that topic, and then it flags
> the
> > topic as migrated and finally it sends migrated-topic response to
> > produ
>
> No, as it's mentioned in PIP: this API will terminate the topic so, it will
> not allow any new write and producers on that topic, and then it flags the
> topic as migrated and finally it sends migrated-topic response to
> producers/caught-up consumers(with 0 backlog) for further redirection.
On Thu, Jul 14, 2022 at 8:29 AM Dave Maughan
wrote:
> Hi Rajan,
>
> Just a note that 184 was already taken by
> https://github.com/apache/pulsar/issues/16481
>
>>> Sure, I have renamed it as PIP-188 and updated the wiki:
https://github.com/apache/pulsar/wiki
- Dave
>
>
> On Tue, Jul 12, 2022 at
This is very interesting.
I have only one concern.
I think that we should at least use a per-tenant system topic, or,
better, per-namespace.
There is no need to create the deletion topic if there is nothing to delete.
I am used to dealing with Pulsar clusters in which Tenants are
strictly isolate
Hi Rajan,
Just a note that 184 was already taken by
https://github.com/apache/pulsar/issues/16481
- Dave
On Tue, Jul 12, 2022 at 6:23 PM Rajan Dhabalia wrote:
> Hi,
>
> We have created PIP-184 which helps users to perform cluster migration with
> Apache Pulsar. Cluster migration or Blue-Green
pgier commented on issue #265:
URL:
https://github.com/apache/pulsar-helm-chart/issues/265#issuecomment-1184585656
If you look at the `app version` of the 2.9.3 release of the Helm chart, you
can see that it still points to version 2.9.2 of Pulsar. However, I agree with
you, that it would
Hi team,
The Pulsar Summit 2022 will be held on August 18th at Hotel Nikko in San
Francisco.
This action-packed, one-day event will include amazing sessions with
speakers from AWS, Klaviyo, Ververica, OneHouse, Nomura, the Apache Pulsar
PMC members, and more! Find the full agenda here [1].
In ad
+1
Thanks,
Haiting
On 2022/07/12 10:00:27 tison wrote:
> Hi,
>
> In the previous email[1] I started a discussion about enabling GitHub
> Discussions in apache/pulsar repository and we meet a consensus to avoid
> making development discussions truth happen on the sources. It's also a
> requiremen
Hello,
this is a PIP to implement a tool to analyse the subscription backlog
Link: https://github.com/apache/pulsar/issues/16597
Prototype: https://github.com/apache/pulsar/pull/16545
Below you can find the proposal (I will amend the GH issue while we
discuss, as usual)
Enrico
Motivation
Curre
11 matches
Mail list logo
