Hi Enrico
Thanks for your replying.
> 1) It is not clear to me if you want to push all the messages metadata
in the main header of the entry or only the metatadata of the first
entry, or only the KEY.
I just want to copy the partial message properties(we call it batch
properties here) to the
Sure, I will take it carefully for those PRs not cherry-picked to branch-2.8
but labeled
as `release/2.8.4`.
Thanks,
Yunze
> 2022年7月22日 00:09，Dave Fisher 写道：
>
> Thank you for volunteering!
>
>> On Jul 21, 2022, at 12:57 AM, Yunze Xu wrote:
>>
>> Hello Pulsar Community,
>>
>> It has
Sorry I’m late to this discussion.
I think that the motivation is correct. There is really quite a bit of activity
around this issue. Let’s take extra efforts to engage extra time with commits
to confirm performance improvements.
Let’s particularly pay attention to threading.
+1
Regards,
+1
Penghui Li
On Jul 22, 2022, 02:37 +0800, Matteo Merli , wrote:
> ## Motivation
>
> The current implementation of the read cache in the Pulsar broker has largely
> remained unchanged for a long time, except for a few minor tweaks.
>
> While the implementation is stable and reasonably efficient
Dear community,
Here's a report of the flaky tests in Pulsar CI during the observation
period of 2022-07-12 - 2022-07-19
https://docs.google.com/spreadsheets/d/165FHpHjs5fHccSsmQM4beeg6brn-zfUjcrXf6xAu4yQ/edit?usp=sharing
The report contains a subset of the test failures.
The flaky tests are
## Motivation
The current implementation of the read cache in the Pulsar broker has largely
remained unchanged for a long time, except for a few minor tweaks.
While the implementation is stable and reasonably efficient for
typical workloads,
the overhead required for managing the cache evictions
Thank you Yunze
I agree that it is time to cut a release of 2.8.
We should also one last release out of 2.7 branch.
I hope that someone will volunteer
Enrico
Il Gio 21 Lug 2022, 18:10 Dave Fisher ha scritto:
> Thank you for volunteering!
>
> > On Jul 21, 2022, at 12:57 AM, Yunze Xu
> wrote:
I understand the need for the Pulsar Summit.
In that case I have to step back because I will be offline for the next few
weeks
Sorry
Nicolò Boschi
Il Gio 21 Lug 2022, 06:32 PengHui Li ha scritto:
> Thanks for volunteering Nicolò.
>
> > So a plan could be to try to merge the work in progress
Thank you for volunteering!
> On Jul 21, 2022, at 12:57 AM, Yunze Xu wrote:
>
> Hello Pulsar Community,
>
> It has been several months since the 2.8.3 release and there are many
> important fixes after that. For example, there is a performance
> regression for message listener that was
Thank you for this proposal !
I understand the problem, and I have already thought about it, because
I am the author of some filters (especially the JMS Selectors Filter)
but we have to clarify more about this PIP.
1) It is not clear to me if you want to push all the messages metadata
in the
Good. +1
Anon Hxy 于2022年7月19日周二 18:00写道：
> Hi Pulsar community:
>
> I open a pip to discuss "Support batched message using entry filter"
>
> Proposal Link: https://github.com/apache/pulsar/issues/16680
> ---
>
> ## Motivation
>
> We already have a plug-in way to filter entries in broker, aka
Hello Pulsar Community,
It has been several months since the 2.8.3 release and there are many
important fixes after that. For example, there is a performance
regression for message listener that was introduced from 2.8.3 and
fixed in https://github.com/apache/pulsar/pull/15162.
I volunteer to be
Il giorno gio 21 lug 2022 alle ore 06:25 PengHui Li
ha scritto:
>
> > What if the topic owner creates an internal subscription, consumes the
> messages, and updates a count per filter.
>
> I agree with this approach. If we need to scan all the backlogs to
> calculate the
> accurate backlogs for
13 matches
Mail list logo
