+1 (non-binding)
- Verified signatures for all 48 artifacts
- Verified sha512 checksums for all 48 artifacts
- Verified rat check by running mvn apache-rat:check
- Compiled from sources using JDK 11 and running mvn clean install -DskipTests
- Inspected docker image mattison/pulsar:2.9.3-rc-2
On Wed, Jul 13, 2022 at 10:57 AM Joe F wrote:
> Hi Rajan,
> >
> > > For consumers, the message will be sent when there are no more messages
> > to
> > > read?
> > >
> > Yes.
>
>
> I think it would be helpful to add a bit more detail on the consumer
> switch (sp. Shared consumers). There is a
+1 (non-binding)
- Download links are valid.
- Checksums and signatures.
- LICENSE/NOTICE/exist
- Rat check passes
- Compile source with JDK11
- Run standalone, and run pulsar produce/consume
Regards
Jiwei Guo (Tboy)
On Wed, Jul 13, 2022 at 11:24 PM Hang Chen wrote:
> +1 (binding)
>
> -
+1
Best,
Max Xu
On Thu, Jul 14, 2022 at 10:17 AM Michael Marshall
wrote:
> +1
>
> - Michael
>
> On Wed, Jul 13, 2022 at 11:05 AM Zixuan Liu wrote:
> >
> > +1
> >
> > Zixuan
> >
> > PengHui Li 于2022年7月13日周三 23:58写道：
> >
> > > +1
> > >
> > > Penghui
> > >
> > > On Wed, Jul 13, 2022 at 11:44
Hi Nicolò,
This is definitely a very awesome job, thank you for bringing Pulsar Shell
to us!
Also, I was wondering if we could integrate the pulsar shell entrypoint
directly into the existing pulsar command[1]? (i.e, invoke ./bin/pulsar
shell)
So that we can reuse the current CLI instead of
michaeljmarshall merged PR #276:
URL: https://github.com/apache/pulsar-helm-chart/pull/276
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
+1
- Michael
On Wed, Jul 13, 2022 at 11:05 AM Zixuan Liu wrote:
>
> +1
>
> Zixuan
>
> PengHui Li 于2022年7月13日周三 23:58写道：
>
> > +1
> >
> > Penghui
> >
> > On Wed, Jul 13, 2022 at 11:44 PM Anon Hxy wrote:
> >
> > > +1
> > >
> > > tison 于2022年7月12日周二 18:01写道：
> > >
> > > > Hi,
> > > >
> > > > In
pgier opened a new pull request, #276:
URL: https://github.com/apache/pulsar-helm-chart/pull/276
This is just a minor improvement to the error handling of one of the bash
scripts
### Motivation
Currently if you run `./scripts/pulsar/prepare_helm_release.sh` and the
pulsar
Hi Rajan,
>
> > For consumers, the message will be sent when there are no more messages
> to
> > read?
> >
> Yes.
I think it would be helpful to add a bit more detail on the consumer
switch (sp. Shared consumers). There is a window of transition where
"dispatched-but-not-acked messages" might
On Wed, Jul 13, 2022 at 2:30 AM Enrico Olivelli wrote:
> Very interesting. Overall I support this proposal
>
> A couple of questions:
> - What about monitoring the status of the migration?
>
There will be a cluster level state. Once all topics are migrated and
deleted, the broker will change
On Wed, Jul 13, 2022 at 1:55 AM Asaf Mesika wrote:
> Few questions
>
> "CompletableFuture asyncMigrate();"
> Does this method only change the status of the managed ledger?
>
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
+1
Penghui
On Wed, Jul 13, 2022 at 11:44 PM Anon Hxy wrote:
> +1
>
> tison 于2022年7月12日周二 18:01写道：
>
> > 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
+1
tison 于2022年7月12日周二 18:01写道：
> 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
> requirement of INFRA team[2]
>
>
Hi Matteo
> Brokers are never going to look into batches, they will just check at the
batch header, without decompression, and not dig into the individual
messages properties
I agree with this. The PIP-105 doesn't support batch send I think. PIP-105
maybe is not a good case for this changing.
+1
--
Matteo Merli
On Wed, Jul 13, 2022 at 7:58 AM Dave Fisher wrote:
>
> +1 - thanks.
>
> Emails will go to dev@pulsar initially. We should have a separate discussion
> about notifications since these are set on a repository by repository basis.
>
> > On Jul 12, 2022, at 4:04 AM, Yu wrote:
+1 (binding)
- Checked the checksum and license
- Build from source code with JDK 11
- Run standalone, and run pulsar-perf produce/consume
- Verified pulsar-io-lakehouse connector
Thanks,
Hang
PengHui Li 于2022年7月8日周五 23:01写道：
>
> +1 binding
>
> - checked the signature
> - run standalone and
+1 - thanks.
Emails will go to dev@pulsar initially. We should have a separate discussion
about notifications since these are set on a repository by repository basis.
> On Jul 12, 2022, at 4:04 AM, Yu wrote:
>
> Hi tison, thanks for creating this vote!
> I thought we reached a lay consensus
tisonkun opened a new issue, #146:
URL: https://github.com/apache/pulsar-site/issues/146
Currently, Pulsar provides a [Client
Libraries](https://pulsar.apache.org/docs/next/client-libraries) page to show
official and third party client libraries.
While it's a good entry point for
Il giorno mer 13 lug 2022 alle ore 04:05 PengHui Li
ha scritto:
>
> Oh, I see.
>
> I think we can start with a proposal? I saw the new REST API introduced in
> the PR.
> It's better to follow the proposal process to get explicit approvals.
Sure.
I started this conversation to understand if
visortelle commented on issue #96:
URL: https://github.com/apache/pulsar-site/issues/96#issuecomment-1182998164
@tisonkun not completely.
It's great that the search spotlight works now!
But in case I click "Search all results", it shows me a forever spinner.
Very interesting. Overall I support this proposal
A couple of questions:
- What about monitoring the status of the migration?
- Should we block all maintenance operations on the "blue" cluster ?
like deleting/creating stuff
- Should we stop ledger trimming and offloading ?
- What about
tisonkun commented on issue #96:
URL: https://github.com/apache/pulsar-site/issues/96#issuecomment-1182960395
It seems the search bar can show results now. Could you check if the issue
resolved?
cc @visortelle
--
This is an automated message from the Apache Git Service.
To
Few questions
"CompletableFuture asyncMigrate();"
Does this method only change the status of the managed ledger?
"message ManagedLedgerInfo {
// Flag to check if topic is terminated and migrated to different cluster
optional bool migrated = 4;
}"
This flag then is only changed to true
Hi Pulsar community: I open a pip to discuss "Introduce two phase deletion
protocol based on system topic" Proposal Link:
https://github.com/apache/pulsar/issues/16569
---
## Motivation
Original issue: #13238
In current ledger deletion, we divided it into two separate steps. It
happens in
+1
On Wed, Jul 13, 2022 at 3:21 PM tison wrote:
>
> Thanks for your feedback. To be clear, I'll conclude the result after 72
> hours from the first email sent if there's no objections.
>
> Best,
> tison.
>
>
> Qiang Huang 于2022年7月13日周三 14:10写道：
>
> > +1
> >
> > guo jiwei 于2022年7月13日周三 10:11写道：
Thanks for your feedback. To be clear, I'll conclude the result after 72
hours from the first email sent if there's no objections.
Best,
tison.
Qiang Huang 于2022年7月13日周三 14:10写道：
> +1
>
> guo jiwei 于2022年7月13日周三 10:11写道：
>
> > +1
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >
> >
> > On Tue,
+1
guo jiwei 于2022年7月13日周三 10:11写道：
> +1
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Tue, Jul 12, 2022 at 9:53 PM Enrico Olivelli
> wrote:
>
> > +1
> >
> >
> > Enrico
> >
> > Il giorno mar 12 lug 2022 alle ore 13:05 Yu ha
> scritto:
> > >
> > > Hi tison, thanks for creating this vote!
> > > I
27 matches
Mail list logo
