+1
mattison chao 于2022年11月7日周一 20:01写道：
> Thanks for volunteering to be the release manager
>
>
> Best,
> Mattison
>
> On Fri, 4 Nov 2022 at 16:28, Haiting Jiang wrote:
>
> > +1
> >
> > Haiting
> >
> > On Fri, Nov 4, 2022 at 1:42 PM houxiaoyu wrote:
> > >
> > > +1
> > >
> > > Best,
> > > Xiaoy
Congratulations, Haiting!
Aloys Zhang 于2022年10月21日周五 11:52写道：
> Congratulations, Haiting!
>
>
> Best，
> Aloys
>
> 丛搏 于2022年10月20日周四 17:11写道：
>
> > Congratulations, Haiting!
> >
> > Thanks,
> > bo
> >
> > PengHui Li 于2022年10月20日周四 16:55写道：
> > >
> > > Congratulations, Haiting!
> > >
> > > Best,
Congratulations Qiang Huang
r...@apache.org 于2022年10月14日周五 17:02写道：
> Congratulations Qiang Huang
>
> --
> Thanks
> XiaolongRan
>
> Nicolò Boschi 于2022年10月14日周五 15:23写道：
>
> > Congrats!
> > Nicolò Boschi
> >
> >
> > Il giorno ven 14 ott 2022 alle ore 09:18 Jiaqi Shen <
> > gleiphir2...@gmail.co
+1 (non-binding)
houxiaoyu 于2022年9月29日周四 16:45写道：
> +1 (non-binding)
>
> - Checksum and signatures
> - Build on Mac, using JDK17
> - Run Pulsar standalone and produce/consume case
>
> Thanks,
> Xiaoyu Hou
>
> Enrico Olivelli 于2022年9月29日周四 16:31写道：
>
> > +1 (binding)
> > - Apache RAT
> > - Signa
+1
Paul Gier 于2022年10月1日周六 05:41写道：
> I thought about this a bit more and realized that ldflags doesn't really
> make sense in this case because this is a library, and we don't control the
> user's build environment. It might work fine for the pulsar-perf binary,
> but doesn't really make sense
NamedEntity#checkName method?
lordcheng10 于2022年10月2日周日 10:19写道：
> > The namespace, cluster and topic names are checked by the
> org.apache.pulsar.common.naming.NamedEntity#checkName method, which
> requires names to contain only (a-zA-Z_0-9) or these special chars -=:.% .
>
&g
the
org.apache.pulsar.common.naming.NamedEntity#checkName method, but the topic
name is the same as the subscription name and is not checked.
lordcheng10 于2022年10月2日周日 10:05写道：
> > I think the subscription name should not contain special characters. It
> should keep the same naming rule wi
; > +1 Add a subscription name naming rule, for example: can only contain
> > these characters "a-zA-Z_0-9" or "-=:.%".
> >
> > I think the subscription name should not contain special characters. It
> > should keep the same naming rule with the topic.
Corresponding PR:
https://github.com/apache/pulsar/pull/17151
lordcheng10 于2022年10月1日周六 11:10写道：
> Hello, Pulsar community:
> When creating a subscription, pulsar does not verify the name of the
> subscription, so the subscription name may contain some invisible
> characters in
Hello, Pulsar community:
When creating a subscription, pulsar does not verify the name of the
subscription, so the subscription name may contain some invisible
characters in the created subscription.
If the subscription name contains some invisible characters, when we delete
the subscription by pul
+1
guo jiwei 于2022年9月1日周四 11:00写道：
> +1 Great work!
>
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Wed, Aug 31, 2022 at 6:19 PM Ran Gao wrote:
>
> > +1 Great work!
> >
> > Thanks,
> > Ran Gao
> >
> > On 2022/08/29 10:37:31 Cong Zhao wrote:
> > > Hi Pulsar Community,
> > >
> > > In order to facilitat
+1
Haiting Jiang 于2022年8月26日周五 09:52写道：
> +1
>
> Thanks,
> Haiting
>
> On Thu, Aug 25, 2022 at 9:52 AM Baodi Shi
> wrote:
>
> > +1
> >
> > Thanks,
> > Baodi Shi
> >
> > > On Aug 24, 2022, at 20:1312, Qiang Huang
> > wrote:
> > >
> > > +1
> > >
> > > Zike Yang 于2022年8月22日周一 15:32写道：
> > >
> >
Thanks for your vote.
Close this vote with 3 (+1) bindings and 5 (+1) non-bindings, 0 (-1).
Thanks for your vote.
Close this vote with 3 (+1) bindings and 5 (+1) non-bindings, 0 (-1)
t; > > > > >
> https://lists.apache.org/thread/cshyt10fwcjjxs93g8yf0svgwcgnshmg
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > > lordcheng10
> > > > >
> > > >
> > >
>
--
BR,
Qiang Huang
w or qps` is based on the entries or messages?"
1. The consumer rate has been considered;
2. The strategy has been based on the entries and throughput;
Thanks,
lordcheng10
Reply for Penghui
he `flow or qps` is based on the entries or messages?
1. The consumer rate has been considered;
2. The strategy has been based on the entries and throughput;
Thanks,
lordcheng10
Hi Pulsar Community, I would like to start a VOTE on "Support split bundle by
flow or qps."(PIP-169)
Here is the design detail: https://github.com/apache/pulsar/issues/16782
and the discussion thread:
https://lists.apache.org/thread/cshyt10fwcjjxs93g8yf0svgwcgnshmg
Thanks,
lordcheng10
Hi Pulsar Community, I would like to start a VOTE on "Support split bundle by
flow or qps."(PIP-169)
Here is the design
detail https://github.com/apache/pulsar/issues/16782 ;
and the discussion
thread https://lists.apache.org/thread/cshyt10fwcjjxs93g8yf0svgwcgnshmg ;
Thanks,
lordcheng10
The implementation logic has been modified, and the corresponding example has
also been modified as follows:
## Motivation
As we all know, Bundle split has 3 algorithms:
- range_equally_divide
- topic_count_equally_divide
- specified_positions_divide
However, none of these algorithms can divid
Nice feature!
-- Original --
From: "Yunze Xu"https://github.com/apache/pulsar/pull/6796 for discussion.
Currently, the Java client acknowledges the specific partition of the
message ID, while the C++ client just fails when calling
`acknowledgeCumulative` on a pa
When the broker is just started, the traffic or QPS may not be stable at this
time.
At this time, we can solve the problem by adjusting the time interval of the
first load reporting task. At present, the time interval for executing the
report task is 5 seconds, and it is not configurable.
I ca
Hi Pulsar Community,
This is a PIP discussion on how to support splitting bundles according to flow
or qps.
The issue can be found: https://github.com/apache/pulsar/issues/16782
I copy the content here for convenience, any suggestions are welcome and
appreciated.
## Motivation
As we all
When the broker is just started, the traffic or QPS may not be stable at this
time.
At this time, we can solve the problem by adjusting the time interval of the
first load reporting task.
The time interval for executing the report task is 5 seconds, and it is not
configurable.
I can add a conf
1. Similar problems also exist in topic_count_equally_divide. In some
scenarios, topics are also temporary, because they will be created and
destroyed continuously.
2. The traffic and qps of most scenarios are relatively stable. For scenarios
where traffic and qps change greatly and frequently,
The PIP number is duplicated, the updated PIP number is PIP-169.
Hi Pulsar Community,
This is a PIP discussion on how to support splitting bundles according to flow
or qps.
The issue can be found: https://github.com/apache/pulsar/issues/16782
I copy the content here for convenience, any suggestions are welcome and
appreciated.
## Motivation
As we all
Here I add, the scene of losing data at that time:
1. For the bookkeeper cluster, we turned off the journal writing function;
2. Then during the upgrade, after executing the stop command several times, the
bookkeeper process does not exit, we will kill -9;
3. Kill -9 will cause the data in the cac
Here is the corresponding fix PR??
https://github.com/apache/pulsar/pull/14645
suggestions are appreciated.
Thanks,
lordcheng10
30 matches
Mail list logo
