+1 (non-binding)
Thanks,
Cong Zhao
On 2024/09/04 04:19:56 "Bhat, Vinay" wrote:
> Hi All,
>
> I want to start a vote on PIP-374: Visibility of messages in receiverQueue
> for the consumers
>
> Proposal link: https://github.com/apache/pulsar/pull/23235
Good work
Thanks
Cong
On 2024/08/30 04:57:01 "Bhat, Vinay" wrote:
> Hi All,
>
> I drafted a proposal for Visibility of messages in receiverQueue for the
> consumers
>
> https://github.com/apache/pulsar/pull/23235
> I'm looking forward to hearing from you.
>
> Thanks
> Vinay
>
I push pr (https://github.com/apache/pulsar-site/pull/912) to regenerate
english javadoc for 3.3.0.
On 2024/06/10 16:48:12 Andrey Yegorov wrote:
> Hello,
>
> Something went wrong with the release Pulsar 3.3 - the JavaDocs are Chinese
> instead of English:
>
> e.g.
> https://pulsar.apache.org/ap
t/cfc7e9d1
> It should prevent this happening in the future by setting the locale property
> for the javadoc task [1]. This is the step used in the release process to
> update the javadocs:
> https://pulsar.apache.org/contribute/release-process/#javadoc
>
> Cong Zhao, wo
The Apache Pulsar team is proud to announce Apache Pulsar version 3.3.0
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for
subscr
1" non-binding votes:
- Andrey Yegorov
I'll continue with the release process and the release announcement will follow
shortly.
Thanks,
Cong
On 2024/06/03 10:51:46 Cong Zhao wrote:
> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache P
README to build
and run the Pulsar standalone service.
More advanced release validation instructions can be found at
https://pulsar.apache.org/contribute/validate-release-candidate/
Thanks,
Cong Zhao
Hello everyone,
Due to https://github.com/apache/pulsar/pull/22804 fix the snappy load issue,
so I will build 3.3.0-candidate-4 as soon as possible.
On 2024/05/29 02:16:59 Cong Zhao wrote:
> Hello all,
>
> The vote to release Apache Pulsar version 3.3.0 based on 3.3.0-candidate-3
inue with the release process and the release announcement will follow
shortly.
Thanks,
Cong
On 2024/05/24 02:28:22 Cong Zhao wrote:
> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache Pulsar version 3.3.0 based
> on 3.3.0-candidate-3.
>
> In
e-3 (commit 0771f818ba74f94b95cd0987997079d0f3e73f94)
> >> > https://github.com/apache/pulsar/releases/tag/v3.3.0-candidate-3
> >> >
> >> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> >> > https://downloads.apache.org/pulsar/KEYS
> >> >
> >> > Docker images:
> >> > docker pull czcoder/pulsar:3.3.0-0771f81
> >> >
> >> >
> >> https://hub.docker.com/layers/czcoder/pulsar/3.3.0-0771f81/images/sha256-e34f1e83bb2a1e8233a3429847bb8fc2cdac0f558a0e5c13658c28773287b07c?context=explore
> >> > docker pull czcoder/pulsar-all:3.3.0-0771f81
> >> >
> >> >
> >> https://hub.docker.com/layers/czcoder/pulsar-all/3.3.0-0771f81/images/sha256-49cf20acab7e71c8916cf594690c86eaaaf8426c8a13013a8c25944338d7be7c?context=explore
> >> >
> >> > Please download the source package, and follow the README to build
> >> > and run the Pulsar standalone service.
> >> >
> >> > More advanced release validation instructions can be found at
> >> > https://pulsar.apache.org/contribute/validate-release-candidate/
> >> >
> >> > Thanks,
> >> > Cong Zhao
> >> >
> >>
> >
>
README to build
and run the Pulsar standalone service.
More advanced release validation instructions can be found at
https://pulsar.apache.org/contribute/validate-release-candidate/
Thanks,
Cong Zhao
> The broker logs show that creating fn using the `default` namespace, but
> geting fn using the `test-namespace`. Then find the related fix in
> https://github.com/apache/pulsar/pull/22209, it adds the default tenant and
> namespace.
>
>
>
>
> On 2024/05/20 04:25
The email title is missing VOTE, please ignore this email.
On 2024/05/20 04:19:54 Cong Zhao wrote:
> Hello Apache Pulsar Community,
>
> This is a call for the vote to release the Apache Pulsar version 3.3.0 based
> on 3.3.0-candidate-2.
>
> Included changes since the previou
README to build
and run the Pulsar standalone service.
More advanced release validation instructions can be found at
https://pulsar.apache.org/contribute/validate-release-candidate/
Thanks,
Cong Zhao
README to build
and run the Pulsar standalone service.
More advanced release validation instructions can be found at
https://pulsar.apache.org/contribute/validate-release-candidate/
Thanks,
Cong Zhao
://github.com/apache/pulsar/pull/22731
I will build 3.3.0 Candidate 2 after the fix PRs are merged.
Regards
Cong Zhao
On 2024/05/17 02:53:28 Yunze Xu wrote:
> -1 (binding)
>
> There seems something wrong with the docker image, see
> https://github.com/BewareMyPower/pulsar-client-cpp/
would also
appreciate your feedback with +1/-1. And please provide specific
comments if your feedback is not +1.
Regards
Cong Zhao
Hi community
I have cut branch 3.3 and will freeze the code for the next two weeks.
Regards
Cong Zhao
On 2024/04/28 12:17:41 Cong Zhao wrote:
> Hi community,
> It has been more than three months since the release of 3.2.0. we now
> have more than 280 commits
> <https://github.co
k for a new 4.17.1 release
>
> Enrico
>
> Il giorno dom 28 apr 2024 alle ore 21:04 PengHui Li ha
> scritto:
>
> > +1
> >
> > Thanks for driving the release.
> >
> > Penghui
> >
> > On Sun, Apr 28, 2024 at 8:17 PM Cong Zhao wrote:
> &g
are some fixes about metrics, maybe we
> could ask for a new 4.17.1 release
>
> Enrico
>
> Il giorno dom 28 apr 2024 alle ore 21:04 PengHui Li ha
> scritto:
>
> > +1
> >
> > Thanks for driving the release.
> >
> > Penghui
> >
>
el%3Atype%2FPIP+>
merged. We'd better prepare for the 3.3.0 release. I would like to cut
branch-3.3 in the next week and freeze the code for two weeks.
Please leave any ideas or concerns.
Regards
Cong Zhao
Congratulations!
Thanks,
Cong
On 2024/02/20 16:50:29 Lari Hotari wrote:
> The Apache Pulsar Project Management Committee (PMC) has invited
> Asaf Mesika https://github.com/asafm to become a committer and we
> are pleased to announce that he has accepted.
>
> Welcome and Congratulations, Asaf Mes
+1 (non-binding)
Thanks,
Cong Zhao
On 2023/11/15 03:59:46 Kevin Lu wrote:
> Hi All,
>
> This thread is to start a vote for PIP-315.
>
> PIP: https://github.com/apache/pulsar/pull/21490
> Discussion thread:
> https://lists.apache.org/thread/285nm08842or324rxc2zy83wxgqxtcjp
>
> Regards,
> Kevin
>
Close the vote with 4+ (binding):
Penghui
Mattison
Yunze
Yubiao
1+(non-binding):
Zixuan
Regards
Cong Zhao
On 2023/11/10 04:12:14 Cong Zhao wrote:
> Hi Community,
>
> This thread is to start a vote for PIP-318.
>
> PIP: https://github.com/apache/pulsar/pull/21541
> Discussio
Congrats! Yubiao
Thanks,
Cong
On 2023/11/13 07:36:27 mattison chao wrote:
> Dear Community,
>
> We are thrilled to announce that Yubiao Feng https://github.com/poorbarcode
> has been invited and has accepted the role of a member of the Apache Pulsar
> Project Management Committee (PMC).
>
>
I think this is a good point.
Thanks,
Cong Zhao
On 2023/10/31 22:21:56 Kevin Lu wrote:
> Hi All,
>
> I just submitted a PIP to add an optional config to limit the max delay
> allowed for delayed delivery. This would be helpful for Pulsar
> administrators if they wanted to provide
Hi Community,
This thread is to start a vote for PIP-318.
PIP: https://github.com/apache/pulsar/pull/21541
Discussion thread:
https://lists.apache.org/thread/68k6vrghfp3np601lrfx5mbfmghbbrjh
Thanks,
Cong Zhao
-pick this fix
into other branches with `compactionRemainNullKey=true` default to keep
compatibility.
Thanks,
Cong Zhao
On 2023/11/08 07:26:30 Enrico Olivelli wrote:
> This is a good point.
>
> Is it worth to make it configurable per topic and per namespace?
>
> Even if this b
Hello everyone,
I open a PIP-318: https://github.com/apache/pulsar/pull/21541 for this
discussion.
Any feedback and suggestions are welcome.
Thanks,
Cong Zhao
On 2023/11/07 02:55:52 Cong Zhao wrote:
> Hi, Pulsar community
>
> Currently, we retain all null-key messages during topic c
Hi mattison,
Thanks for your suggestion, I agree with you, we can add a configuration to
smooth the migrate this change.
Let's see if anyone else has any other ideas, and if everyone agrees with this
approach, I'll implement it.
Thanks,
Cong Zhao
On 2023/11/07 03:03:58 mattison
ining all null-key messages will double the storage cost,
and we'll never be able to clean them up since the compacted topic has not
supported the retention policy yet.
In summary, I don't think we should retain null-key messages during topic
compaction.
Looking forward to your feedback
+1(no-binding)
Thanks,
Cong Zhao
On 2023/10/19 12:47:45 guo jiwei wrote:
> Hi dev,
>Currently WebSocket only supports the consumption of a single topic,
> which cannot satisfy users' consumption scenarios of multiple topics. So
> in order to support consumption of multiple
Thanks.
Close the vote with 3+ (binding):
Penghui
Mattison
Jiwei Guo
1+(non-binding):
Zike
Regards
Cong Zhao
On 2023/09/14 03:23:29 Cong Zhao wrote:
> Hi, all
>
> Since there are no other concerns in the discussion, I'm delighted to
> start the voting process for the PIP-286.
Hi, all
Since there are no other concerns in the discussion, I'm delighted to
start the voting process for the PIP-286.
Here is the link to the PIP: https://github.com/apache/pulsar/pull/20867
Thanks,
Cong Zhao
s the entry directly instead of RawEntryMetadata to avoid
introducing a new interface, it's important to note that the caller needs to
release it manually.
I already updated the proposal, please help review it.
Thanks,
Cong Zhao
On 2023/07/25 04:12:09 Cong Zhao wrote:
> Hi Pulsar Comm
be called again to call
the readCompactedEntries method.
Thanks,
Cong Zhao
On 2023/08/28 01:31:14 PengHui Li wrote:
> Hi Cong,
>
> Thanks for driving the proposal.
> Is it better to use `readNewestCompactedEntry(@Nonnull
> Predicate condition)`
>
> So that you don
ng ledgers.
Looking forward to your feedback!
Best regards,
Cong Zhao
Great!
+1 non-binding
Thanks,
Cong Zhao
On 2023/08/05 04:14:24 tison wrote:
> Hi,
>
> I'd like to start a vote thread for accepting pulsar-admin-go[1] as part of
> the Apache Pulsar project. pulsar-admin-go is a Golang client library
> interacting with Pulsar Admin API.
Hi Pulsar Community, I am writing to start the discussion on PIP 286 PR
with PIP contents: https://github.com/apache/pulsar/pull/20867 Thanks,
Cong Zhao
Close this vote by
3 binding +1s
* Qiang Zhao
* Yunze Xu
* PengHui Li
Thanks,
Cong Zhao
On 2023/06/26 02:01:06 Cong Zhao wrote:
> Hello, community:
>
> This thread is to start a vote for PIP-278: Support pluggable topic
> compaction service.
>
> Discussion thread:
> htt
Hello, community:
This thread is to start a vote for PIP-278: Support pluggable topic
compaction service.
Discussion thread:
https://lists.apache.org/thread/ox2bot3p9j9fydqkw3v5gt5twc8jslvd
PIP PR: https://github.com/apache/pulsar/pull/20624
Sincerely
Cong Zhao
Hi Pulsar Community,
I am writing to start the discussion on PIP 278 to support pluggable compaction
service
PR with PIP contents: https://github.com/apache/pulsar/pull/20624
Thanks,
Cong Zhao
Hi Pulsar Community,
I am writing to start the discussion on PIP 274 to support pluggable topic
compactor
PR with PIP contents: https://github.com/apache/pulsar/pull/20493
Thanks,
Cong Zhao
The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.5.
Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, automatic cursor management
for
subsc
Hi Lari Hotar,
I would like to pick up this work, I will update
https://github.com/apache/pulsar/pull/16832 as soon.
Thanks,
Cong Zhao
On 2023/04/26 15:17:37 Lari Hotari wrote:
> Hi all,
>
> Pulsar doesn't support cgroup v2 which becomes default in Kubernetes v1.25+.
> Kubern
I agree with this, other PRs can move to 3.0.1.
Thanks,
Cong Zhao
On 2023/04/21 09:43:20 Christophe Bornet wrote:
> So to respect the code freeze, I propose to revert all those commits except:
> https://github.com/apache/pulsar/pull/19849
> https://github.com/apache/pulsar/pull/200
PRs are optimized for large amounts of data, we also can
discuss whether they are necessary to cherry-pick into 3.0.
Thanks,
Cong Zhao
On 2023/04/21 07:26:43 Nicolò Boschi wrote:
> I believe that currently there's no clear process in place in order to
> decide whether a commit shoul
20117
https://github.com/apache/pulsar/pull/20155
https://github.com/apache/pulsar/pull/20156
https://github.com/apache/pulsar/pull/20158
Thanks,
Cong Zhao
On 2023/04/21 05:36:26 Zike Yang wrote:
> Hi, all
>
> We found that there were a lot of commits that were cherry-picked to
> branc
Close this vote with 4 +1 (binding)
- Mattison
- Penghui
- Jiwei
- Yunze
On 2023/04/10 07:38:09 Cong Zhao wrote:
> This is the third release candidate for Apache Pulsar, version 2.9.5.
>
> This release contains 105 commits by 32 contributors.
> https://github.com/apache/pulsar/co
I think this is a good idea for the reasonable use of pulsar threads.
Thanks,
Cong Zhao
On 2023/04/18 02:07:55 mattisonc...@gmail.com wrote:
>
> Hello, folks.
>
> I would like to start discussing the pulsar internal thread pool sorting out.
>
> How did I get this idea?
>
ha256-d857951e85b41fe7172769380ffbcac126c75dc476fdcb4755623600b3eb03e0?context=explore
Please download the source package, and follow the README to build
and run the Pulsar standalone service.
Thanks
Cong Zhao
+1, I support removing it if the code isn't being used or maintained.
Thanks,
Cong Zhao
On 2023/04/04 06:47:24 Enrico Olivelli wrote:
> Hello,
> It has been a long time that we have in the Pulsar code a new
> experimental Dispatcher implementation named StreamingDispatch
>
> Thanks
> Yubiao Feng
>
> [1] https://github.com/apache/pulsar/pull/19989
>
> On Mon, Mar 27, 2023 at 11:09 PM Cong Zhao wrote:
>
> > This is the third release candidate for Apache Pulsar, version 2.9.5.
> >
> > This release contains 103 commits by
ld wait for this
> > PR merge,
> >
> > Thanks
> > Yubiao Feng
> >
> > [1] https://github.com/apache/pulsar/pull/19989
> >
> > On Mon, Mar 27, 2023 at 11:09 PM Cong Zhao wrote:
> >
> > > This is the third release candidate for Apache Pulsar,
Congrats! Qiang.
Thanks,
Cong Zhao
On 2023/03/29 03:22:43 guo jiwei wrote:
> Dear Community,
>
> We are thrilled to announce that Qiang Zhao
> (https://github.com/mattisonchao) has been invited and has accepted the
> role of member of the Apache Pulsar Project Management
ha256-c43a489c65cf6c407d6c3be6fc7a001227805b1aaa9413115cf55ba11a1e329f?context=explore
Please download the source package, and follow the README to build
and run the Pulsar standalone service.
Thanks
Cong Zhao
Hi, community,
Sorry to tell everyone that we may need to abort the release
2.9.5-candidate-1 due to license problem.
Please forward to 2.9.5-candidate-2 [0]
Thanks
Cong Zhao
[0]: https://lists.apache.org/thread/nkylf740pwwvb4g0b4dtplqn4lyrp4lv
On 2023/03/20 04:00:56 Cong Zhao wrote:
> T
ha256-c43a489c65cf6c407d6c3be6fc7a001227805b1aaa9413115cf55ba11a1e329f?context=explore
Please download the source package, and follow the README to build
and run the Pulsar standalone service.
Thanks
Cong Zhao
+1 (non-binding)
Thanks,
Cong Zhao
On 2023/03/15 07:54:20 Yunze Xu wrote:
> Hi all,
>
> This thread is to start the vote for PIP-254.
>
> Discussion thread:
> https://lists.apache.org/thread/65cf7w76tt23sbsjnr8rpfxqf1nt9s9l
>
> PIP link: https://github.com/ap
This is the third release candidate for Apache Pulsar, version 2.9.5.
This release contains 82 commits by 30 contributors.
https://github.com/apache/pulsar/compare/v2.9.4...v2.9.5-candidate-1
*** Please download, test, and vote on this release. This vote will stay
open
for at least 72 hours ***
Hello, Pulsar community:
The cherry-pick of 2.9.5 is primarily completed.
Contains 80 PRs [0].
If you have some PRs that must be included in release-2.9.5, you can reply
to me in the email.
I will wait for these PRs to be completed before releasing 2.9.5.
Thanks,
Cong
[0]
https://github.com/apa
+1 Looks great!
Thanks,
Cong
> 2023年2月18日 06:44，Matteo Merli 写道：
>
> Since the LTS release model has been formally approved, I'm proposing
> the following schedule for the release:
>
> * Tue - 2023-05-11
> - RC-1
> - Code Freeze -- Only critical fixes will be merged in the 3.0
> rele
+1 Looks great!
Thanks,
Cong
On 2023/02/17 22:44:34 Matteo Merli wrote:
> Since the LTS release model has been formally approved, I'm proposing
> the following schedule for the release:
>
> * Tue - 2023-05-11
>- RC-1
>- Code Freeze -- Only critical fixes will be merged in the 3.
+1 (non-binding)
Thanks,
Cong
On 2023/02/18 08:58:26 mattisonc...@gmail.com wrote:
> Hi, All
>
> After a fascinating discussion, I would start the vote of PIP-242.
>
> We have chosen to drop out the `system topic` related improvement to another
> PIP. Therefore, the current version is simple e
Congratulations!
Thanks,
Cong
On 2023/01/20 12:36:54 Lari Hotari wrote:
> Dear Community,
>
> We are thrilled to announce that Nicolò Boschi
> (https://github.com/nicoloboschi) has been invited and has accepted the
> role of member of the Apache Pulsar Project Management Committee (PMC).
>
> Ni
Congratulations!
Thanks,
Cong
On 2023/01/18 13:50:12 PengHui Li wrote:
> Hi all,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Bo Cong
> (https://github.com/congbobo184) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
> He is very active in
Congratulations!
Thanks,
Cong
On 2023/01/18 13:35:41 Yunze Xu wrote:
> The Project Management Committee (PMC) for Apache Pulsar has invited
> Baodi Shi (https://github.com/shibd) to become a committer and we are
> pleased to announce that he has accepted.
>
> Being a committer enables easier con
+1
Thanks,
Cong
On 2022/12/19 10:19:07 mattisonc...@gmail.com wrote:
>
> Hi, All
>
> I would like to introduce a new library oshi[1] to help Apache Pulsar sensory
> OS resources. It can help us to get away from the complex file manipulation
> and cross-platform compatibility issues in some op
Congratulations! Yunze
Best,
Cong
On 2022/12/29 12:42:36 Haiting Jiang wrote:
> Hi all,
>
> The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu
> (https://github.com/BewareMyPower) as a member of the PMC and we are
> pleased to announce that he has accepted.
>
> He is very
+1(non-binding)
Thanks,
Cong
On 2022/11/01 14:28:14 linlin wrote:
> Hi folks,
>
> I'd like to start a vote for the PIP-219: Support full scan and trim ledger
> (
> https://github.com/apache/pulsar/issues/18128)
>
> The discussion can be found here:
> https://lists.apache.org/thread/wy8sqs2fdmw3
Hi,
The vote for PIP-195: New bucket based delayed message tracker passed with 3
+1 (binding) and 2 +1 (non-binding).
+1 (binding)
- Penghui
- Jiwei Guo
- Enrico Olivelli
+1 (non-binding)
- Ran Gao
- lordcheng
Thanks,
Cong Zhao
On 2022/08/08 06:51:31 Cong Zhao wrote:
> Hi Pulsar Commun
Hi Pulsar Community,
In order to facilitate community review, I copied this proposal to Google Docs,
please review it and complete the vote.
PIP:
https://docs.google.com/document/d/17HE88w4WuEsLoz0DExPpRN555UC_Tc3MEIKckVWksDc/edit
On 2022/08/08 06:51:31 Cong Zhao wrote:
> Hi Pulsar Commun
Congratulations!
Thanks,
Cong Zhao
On 2022/08/18 11:24:01 PengHui Li wrote:
> Hi, all
>
> I'm glad to announce that the Apache Pulsar PMC invited Jiwei Guo to join
> the
> PMC and he accepted.
>
> Please join in celebrating!
>
> Best,
> Penghui
>
z4
Voting will stay open for at least 48h.
Thanks,
Cong Zhao
Hi Penghui,
Thanks for your feed.
I have added them, please see the proposal again.
Thanks,
Cong Zhao
On 2022/07/29 05:08:10 PengHui Li wrote:
> We should also add a part for observability. Add some metrics to the delayed
> index buckets and snapshots will help users to tu
pens if you have brokers that are still running the old
> tracker?
>
> Is it possible to rollback seamlessly?
>
> Enrico
>
> Il Mer 27 Lug 2022, 05:39 Dezhi Liu ha scritto:
>
> > +1, good job.
> >
> > Thanks,
> > Dezhi
> >
> > On 2022
Hello Pulsar Community,
I would like to open a discussion here about PIP-195 : New bucket based
delayed message tracker. I look forward to your feedback.
PIP: https://github.com/apache/pulsar/issues/16763
Thanks,
Cong Zhao
cluster for auto-failover cases should be better than just
probing the port before.
Thanks,
Cong Zhao
On 2022/07/01 05:47:46 Michael Marshall wrote:
> Thanks for your response Cong Zhao.
>
> > I think don't need to handle it, because the client API should be
> > consi
I forgot to close this vote.
I'm closing the vote.
The proposal has been accepted with 4 binding +1, non-binding +1 votes.
Thanks,
Cong Zhao
On 2022/05/26 13:40:30 zhaocong wrote:
> Hi Pulsar Community,
>
>
> I would like to start a VOTE on "Support zero-copy of NIC t
Thanks for your participation.
I'm closing the vote.
The proposal has been accepted with 5 binding +1, non-binding +2 votes.
On 2022/06/17 01:21:14 Cong Zhao wrote:
> Hi Pulsar Community,
>
>
> I would like to start a VOTE on "Add the classLoader field for
> S
Also, for the main problem that this proposal wants to solve (how to check a
new cluster is healthy). Do you have another better idea?
Thanks,
Cong Zhao
On 2022/06/24 05:25:46 Michael Marshall wrote:
> Thanks for your replies Cong Zhao.
>
> I think the current PIP might need some c
k whether there is available topic
in the cluster, and I think this is meaningful in most cases.
I think if the client implementation doesn't meet the user's needs, they can
also override the `healthCheck` method based on the `HEALTH_CHECK` command.
Thanks,
Cong Zhao
On 2022/06/22 19:06
Yes, there may have multiple clients request the HC at the same time in the
AutoFailover case, so we should add some cache to reduce broker load.
On 2022/06/22 12:55:49 Enrico Olivelli wrote:
> Il giorno mer 22 giu 2022 alle ore 14:45 Cong Zhao
> ha scritto:
> >
> > Hi Enrico,
gt; Il giorno mer 8 giu 2022 alle ore 05:22 zhaocong
> ha scritto:
> >
> > Hello Pulsar Community,
> >
> >
> > Here is a PIP to introduce the HEALTH_CHECK command in the binary protocol.
> > I look forward to your feedback.
> >
> >
> > PIP: https://github.com/apache/pulsar/issues/15859
> >
> >
> > Thanks,
> >
> > Cong Zhao
>
org/thread/6td3wyfybsys4vf1tgf7fxy36w10nb5k
Voting will stay open for at least 48h.
Thanks,
Cong Zhao
7ckyrcgfhf
Voting will stay open for at least 48h.
Thanks,
Cong Zhao
The priority of the classLoader field will be higher than by the
pojoClass.getClassLoader() if with non JSON Schemas.
On 2022/06/14 18:54:15 Enrico Olivelli wrote:
> Hello,
> how will it work with non JSON Schemas ?
>
> Enrico
>
> Il giorno mar 14 giu 2022 alle ore 17:
Hello Pulsar Community,
Here is a PIP to add the classLoader field for SchemaDefinition. I look
forward to your feedback.
PIP: https://github.com/apache/pulsar/issues/16058
Thanks,
Cong Zhao
; The proposal can be read at https://github.com/apache/pulsar/issues/15631
> >
> > and the discussion thead is available at
> >
> > https://lists.apache.org/thread/gjys9tvbd5hy28mbkbcq7wkqfldycn7v
> >
> >
> > Voting will stay open for at least 48h.
> >
> >
> > Thanks,
> >
> > Cong Zhao
> >
>
Hello Pulsar Community,
Here is a PIP to support zero-copy of NIC to NIC on the proxy server. I
look forward to your feedback.
PIP: https://github.com/apache/pulsar/issues/15631
Thanks,
Cong Zhao
sorry, I made a mistake. I'll send another one
On Fri, May 20, 2022 at 10:09 AM Cong Zhao wrote:
> Hello Pulsar Community,
>
> Here is a PIP to support zero-copy of NIC to NIC on the proxy server. I
> look forward to your feedback.
>
> PIP: https://github.com/apache/pul
Hello Pulsar Community,
Here is a PIP to support zero-copy of NIC to NIC on the proxy server. I
look forward to your feedback.
PIP: https://github.com/apache/pulsar/issues/15597 Thanks, Cong Zhao
92 matches
Mail list logo
