Hi Lin Lin
Which version you are working on the test?
Do you have any steps to reproduce the issue?
We'd better fix the problem in 2.10.
Regards,
Penghui
On Tue, Dec 21, 2021 at 11:06 AM Lin Lin wrote:
>
>
> On 2021/12/14 18:03:20 Matteo Merli wrote:
> > https://github.com/apache/pulsar/issues
+1 (binding)
- check signatures/checksums
- Built sources
- Validate Pub/Sub and Java Functions
- Validate Connectors
- Validate Stateful Functions
Regards,
Hiroyuki
From: linlin
Sent: Monday, December 20, 2021 20:18
To: dev@pulsar.apache.org
Subject: [V
On 2021/12/14 18:03:20 Matteo Merli wrote:
> https://github.com/apache/pulsar/issues/13304
>
>
> Pasted below for quoting convenience.
>
> ---
>
>
> ## Motivation
>
> After all the work done for PIP-45 that was already included in 2.8 and 2.9
> releases, it enabled the concept of re-ac
Hi, community.
Due to the CVE-2021-25105 (more details at
https://logging.apache.org/log4j/2.x/security.html), we have to upgrade
log4j2 to 2.17, so suggest canceling this vote.
I will send out the second-round vote later.
Regards
Jiwei Guo (Tboy)
On Mon, Dec 20, 2021 at 6:39 PM Nozomi Kurihar
Matt-Esch commented on issue #99:
URL:
https://github.com/apache/pulsar-client-node/issues/99#issuecomment-998386200
Can confirm this is an issue, occurs when upgrading to pulsar > 2.6.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
+1
On Tue, 21 Dec 2021 at 06:30, Michael Marshall wrote:
> +1
>
> On Thu, Dec 16, 2021 at 10:37 PM Sijie Guo wrote:
> >
> > +1
> >
> > On Tue, Dec 14, 2021 at 10:15 AM Matteo Merli wrote:
> >
> > > Pasted below for quoting convenience.
> > >
> > >
> > >
> > >
> > > ## Motivation
> > >
+1
On Thu, Dec 16, 2021 at 10:37 PM Sijie Guo wrote:
>
> +1
>
> On Tue, Dec 14, 2021 at 10:15 AM Matteo Merli wrote:
>
> > Pasted below for quoting convenience.
> >
> >
> >
> >
> > ## Motivation
> >
> > The consistent hashing implementation to uniformly assign keys to consumers
> > in t
+1 sounds like a great improvement.
> With the re-acquirable resource locks, that problem was solved and thoroughly
> tested to be robust.
I haven't been able to follow the PIP 45 work, so I have some high
level questions. Do we have documentation on the implementation of
these re-acquirable reso
> I think it's a good time for 2.10 to enable this setting by default and,
> correspondingly, to disable by default the producer queue size limit.
+1
> 64MB is picked because it's a small enough memory size that will guarantee
> a very high producer throughput, irrespective of the individual mess
Thanks for creating this PIP Zike Yang. This sounds like an important
improvement. I have a couple thoughts.
1. Does the `retryLetterTopic` have the same problem with immediate
message expiration? Based on a quick glance, I don't see anything
creating a subscription for the retry topic.
2. Your p
Thank you Penghui, Technoboy, and BewareMyPower for picking up where I
left off to get the 2.7.4 release ready to go. You cherry-picked many commits,
resolved many conflicts, and fixed a bunch of tests!
Thanks,
Michael
On Thu, Dec 16, 2021 at 7:37 PM guo jiwei wrote:
>
> Hi,
> After we have fix
tschmidt64-SC commented on issue #134:
URL:
https://github.com/apache/pulsar-client-node/issues/134#issuecomment-998219865
I'm still having this issue to this day. Tried building in a docker
container, same issue there.
--
This is an automated message from the Apache Git Service.
To re
Hi Pulsar Community,
I would like to clean up our main project's `docker/` directory. We
have a couple of old Dockerfiles that either need to be updated or
removed. My vote is to remove them.
1. Grafana: with every release, we build and upload a custom grafana
docker image just to package dashboa
+1 (binding)
Check signature,
Run standalone,
Verify Cassandra connector,
Verify Function
Verify PusarSQL, still have `java.nio.BufferUnderflowException`, but it
only happens on the topic created by the Function,
I have tried to publish new string messages to a new topic, and query data
from the t
eolivelli commented on issue #29:
URL: https://github.com/apache/pulsar-adapters/issues/29#issuecomment-998040594
> Can raise a PR if that's fine
Sure! thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
(changing the subject)
Il giorno lun 20 dic 2021 alle ore 13:33 PengHui Li ha
scritto:
> I use the 2.9.1 tag to run the test, not branch-2.9.
>
> I think this one(2db23b8dd3eb859cc16e30686578be275026c347) is the last one
> that you cherry-picked?
>
This is the latest commit: f52ac045f41acbb6c3
I use the 2.9.1 tag to run the test, not branch-2.9.
I think this one(2db23b8dd3eb859cc16e30686578be275026c347) is the last one
that you cherry-picked?
But there are failed tests:
[image: image.png]
Penghui
On Mon, Dec 20, 2021 at 8:24 PM Enrico Olivelli wrote:
> Il giorno lun 20 dic 2021 al
Il giorno lun 20 dic 2021 alle ore 13:21 PengHui Li ha
scritto:
> Hi Enrico,
>
> Have you checked the CI status after completing the 2.9.1 PRs
> cherry-picking?
>
When I created the tag I am pretty sure that CI on GH actions passed.
I hope that no-one committed something to branch-2.9
If this
Hi Enrico,
Have you checked the CI status after completing the 2.9.1 PRs
cherry-picking?
Looks this test failed when I run the test with tag 2.9.1.
```
[INFO] Running org.apache.pulsar.broker.transaction.TransactionTest
[ERROR] Tests run: 14, Failures: 1, Errors: 0, Skipped: 12, Time elapsed:
26
This is the second release candidate for Apache Pulsar, version 2.8.2
It fixes the following issues:
https://github.com/apache/pulsar/issues?q=label%3Acherry-picked%2Fbranch-2.8+label%3Arelease%2F2.8.2+is%3Aclosed
*** Please download, test and vote on this release. This vote will stay open
for at
Hi Dave,
Thanks for your instructions.
+1 for not migrating the incubating versioned docs since they are too old
and almost no one uses them. Besides, as you suggested, we can regenerate
those docs if needed.
On Mon, Dec 20, 2021 at 11:18 AM Dave Fisher wrote:
> This is a question for the dev@
+1 (binding)
- verified checksums and signatures
- build from source
- verified produce/consume and functions
- verified cassandra connector
- verified stateful function
Thanks,
Nozomi
2021年12月18日(土) 19:43 Enrico Olivelli :
> Jiwei Guo,
> Thanks for driving the release
> today is Saturday, so I
https://github.com/apache/pulsar/issues/13408
Pasted below for quoting convenience.
——
## Motivation
If we enable the DLQ when consuming messages. For some messages that can't be
processed successfully, the messages will be moved to the DLQ, but if we do not
specify the data retention for th
Yu,
Il giorno lun 20 dic 2021 alle ore 10:01 Yu ha scritto:
> Hi Enrico,
>
> Thanks for your contribution.
>
> 1) A soft reminder that is not on the current release process [a]:
> Since 2.9.0 was delayed, some doc changes on the master are applied to
> 2.10.0 only, so generating the 2.9.0 doc se
Hi Enrico,
Thanks for your contribution.
1) A soft reminder that is not on the current release process [a]:
Since 2.9.0 was delayed, some doc changes on the master are applied to
2.10.0 only, so generating the 2.9.0 doc set should be based on the "2.9.0
release time point" rather than the current
aditiwari01 commented on issue #29:
URL: https://github.com/apache/pulsar-adapters/issues/29#issuecomment-997713940
The current available spark pulsar adapter seems to be unreliable. I've
written a reliable connector with addition consideration for back-pressure and
rate limit. Currently t
26 matches
Mail list logo
