Re: [VOTE] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-3

If the snappy in zookeeper is not used very commonly, this might not be a blocker for this release. So I would be -0. Thanks, Yong On Fri, 24 May 2024 at 15:17, Yong Zhang wrote: > -1 > > There is an issue with the snappy usage in the amd64-based image. > > It wil

Re: [VOTE] Release Apache Pulsar 3.3.0 based on 3.3.0-candidate-3

-1 There is an issue with the snappy usage in the amd64-based image. It will get the error java.lang.UnsatisfiedLinkError: /tmp/ snappy-1.1.10-b0757287-8557-44b9-9499-afca52f102ec-libsnappyjava.so: Error relocating /lib/ld-linux-x86-64.so.2: unsupported relocation type 37. Reproduce steps: 1. d

Re: [VOTE] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis

> Thanks > > > ZhangJian He > > > Twitter: shoothzj > > > Wechat: shoothzj > > > > > > > > > On Mon, May 13, 2024 at 2:35 PM Hang Chen wrote: > > > > > > > +1 (binding) > > > > > > > > Thanks,

[VOTE] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis

Hi, I would like to start voting thread for PIP-350. https://github.com/apache/pulsar/pull/22688 The implementation PR is: https://github.com/apache/pulsar/pull/22689 Discuss thread: https://lists.apache.org/thread/7tlpkcm2933ddg95kgrb42943r4gq3v9 Thanks, Yong

[DISCUSS] PIP-350: Allow to disable the managedLedgerOffloadDeletionLagInMillis

Hi all, I pushed a new proposal to allow to use -1 to disable the managedLedgerOffloadDeletionLagInMillis to not delete the data from bookkeeper. Please take a look and share your thoughts. Thanks! PIP: https://github.com/apache/pulsar/pull/22688 Best Regards, Yong

Re: [VOTE] Accept pulsar-admin-go as part of the Apache Pulsar project

Great! +1 non-binding Thanks, Yong On Sat, 5 Aug 2023 at 23:17, 太上玄元道君 wrote: > +1 non-binding > > Thanks, > Tao Jiuming > > Zixuan Liu 于2023年8月5日 周六22:58写道： > > > +1 (non-binding) > > > > Thanks, > > Zixuan > > > > 于2023年8月5日周六 21:11写道： > > > > > > +1 (binding) > > > > > > Best, > > > Matti

Re: Improving the usability of the bookie Isolation feature

Overall looks good. Can you please convert this to a PIP and push a PR for it? Then I think we can go to implement. -- Yong On Mon, 26 Jun 2023 at 15:23, Enrico Olivelli wrote: > Il giorno lun 26 giu 2023 alle ore 09:21 Yubiao Feng > ha scritto: > > > > Hi Yan,Asaf > > > > > I want to add onl

Re: [DISCUSS] new idea: reverse reading a topic

, > > Michael > > > > On Tue, Mar 7, 2023 at 6:50 AM Alexandre DUVAL > wrote: > >> Hi Yong, > >> > >> The goal is to start from a known MessageId and read the N message > >> before this MessageId. > >> > >> Best, > >&g

Re: [DISCUSS] new idea: reverse reading a topic

Hi Kannar, Just interested in what exactly your case. Why do you need to read messages in a reversed order? What is your case? Best, Yong On Mon, 6 Mar 2023 at 23:37, Alexandre DUVAL wrote: > Hi, > > I'm wondering if it is possible to introduce a new feature on Pulsar > which will enable user

Re: [DISCUSS] Topic name restriction

t of names makes it easier for > forwards > > > > > > > > compatibility. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Michael > > > > > > > > > > > > > > > > [0] > > > >

Re: [DISCUSS] Topic name restriction

Mattison, I agree with you about restricting the topic name. How about using a blacklist way to restrict it? We can have a blacklist on the topic name restriction and make it configurable. Add the keywords you mentioned in the default configuration. That would have a more general way to block a

Re: Zookeeper exception handler in Pulsar

s? > > > We need to do some work on the metastore and managed ledger to keep the > > consistency between them. But that would change most of the callback of > the > > meta store to handle it. > > This sounds reasonable. Would you be able to share more details about this >

Zookeeper exception handler in Pulsar

Hi all, I saw in the Pulsar Metadata handler, we retry the operation when zookeeper throws a connection loss exception. But the operation may fail after the retry. For example, we update the ledgers map in memory after successfully updating the LedgerInfo in the zookeeper. If the zookeeper update

Re: [ANNOUNCE] New committer: Rui Fu

Congratulations! On Wed, 11 Aug 2021 at 11:20, r...@apache.org wrote: > Congrats Rui! > > -- > Thanks > Xiaolong Ran > > Aloys Zhang 于2021年8月11日周三 上午1:44写道： > > > Congrats Rui! > > > > PengHui Li 于2021年8月10日周二 下午11:42写道： > > > > > Congrats Rui! > > > > > > Penghui > > > On Aug 10, 2021, 8:43 P

Re: [ANNOUNCE] New PMC member: Enrico Olivelli (eolivelli)

Congrats Enrico! On Tue, 3 Aug 2021 at 20:20, Guangning E wrote: > Congrats! > > Ivan Kelly 于2021年8月3日周二 下午7:43写道： > > > Congrats Enrico! > > > > On Tue, Aug 3, 2021 at 12:19 PM Jia Zhai wrote: > > > > > > Congrats Enrico! > > > > > > Best Regards. > > > > > > > > > Jia Zhai > > > > > > Beijin

Re: [ANNOUNCE] New PMC member: Lin Lin (@315157973)

Congrats! Yong On Wed, 4 Aug 2021 at 09:03, Jia Zhai wrote: > Congrats Lin Lin! > > Best Regards. > > > Jia Zhai > > Beijing, China > > Mobile: +86 15810491983 > > > > > On Tue, Aug 3, 2021 at 8:21 PM Guangning E wrote: > > > Congrats! > > > > guo jiwei 于2021年8月3日周二 下午6:16写道： > > > > > Congr

Re: [ANNOUNCE] New PMC member: Hang Chen

Congrats Hang Regards, Yong On Wed, 4 Aug 2021 at 19:21, Aloys Zhang wrote: > Congrats！ > > Jinfeng Huang 于2021年8月4日周三 下午1:36写道： > > > Congrats Hang > > > > Best Regards, > > Jennifer > > > > > > On Wed, Aug 4, 2021 at 10:41 AM r...@apache.org > > > wrote: > > > > > Congrats chen hang > > > >

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

+1 checked: - binary package checksum and signature - run standalone service with the binary package, produce and consume messages - run stateful function with the binary package - source package checksum and signature - compile the source package, and run standalone service, produce and consume m

Re: [VOTE] Pulsar Client Go Release 0.6.0 Candidate 1

+1 - verified checksum - run produce and consume Regards, Yong On Wed, 21 Jul 2021 at 15:34, r...@apache.org wrote: > Hi everyone, > > > Please review and vote on the release candidate #1 for the version 0.6.0, > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the releas

Re: [DISCUSS] Fix 2.7.1 DEB and RPM packages

e 12:29 Guangning E > ha scritto: > > > > +1 > > I don't think you need to change the tarball, just upload the missing deb > > and rpm packages so that users can continue to use the tarball and the > > unpacked packages > > > > Thanks, > > Guan

[DISCUSS] Fix 2.7.1 DEB and RPM packages

Hi all， When releasing 2.7.1 DEB and RPMs packages I upload them as a tarball and that will make some user can not download them properly. So I want to decompress them and reupload it to solve that problem. What do you think? https://dist.apache.org/repos/dist/release/pulsar/pulsar-2.7.1/DEB/ ht

[ANNOUNCE] Apache Pulsar 2.7.1 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.7.1. 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

Re: [VOTE] Pulsar Release 2.7.1 Candidate 1

rce looks good (Maven Rat) > > > Source compiled and tests passed (OSX, Java 1.8) > > > Run simple standalone server > > > No binary files in source artifact > > > > > > +1 (Non-binding) > > > > > > - Henry > > > > > > &

Re: [VOTE] Pulsar Release 2.7.1 Candidate 1

gainst the one in > /release/ directory, right? > > - Henry > > On Tue, Mar 9, 2021 at 2:48 AM Yong Zhang > wrote: > > > For the signature issue, I think we should use this keys > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > I updated the Pu

Re: [VOTE] Pulsar Release 2.7.1 Candidate 1

r.java:225) > > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode > (Launcher.java:406) > > at org.codehaus.plexus.classworlds.launcher.Launcher.main > (Launcher.java:347) > > Il giorno mar 9 mar 2021 alle ore 08:04 Enrico Olivelli > h

[VOTE] Pulsar Release 2.7.1 Candidate 1

Hi all. This is the first release candidate for Apache Pulsar, version 2.X.0. It fixes the following issues: https://github.com/apache/pulsar/pulls?page=1&q=is%3Apr+label%3Arelease%2F2.7.1+is%3Aclosed+-label%3Acomponent%2Fdocumentation *** Please download, test and vote on this release. This vot

Re: [VOTE] Pulsar Client Go Release 0.4.0 Candidate 1

+1 - Run produce and consumer and reader - The signature looks good now ``` gpg: Signature made 五 3/ 5 11:28:12 2021 CST gpg:using RSA key C6027CC38D525CEAF0256A74772D77990D717CBC gpg: Good signature from "Penghui Li (CODE SIGNING KEY) " [unknown] gpg: WARNING: This key is not ce

Re: [DISCUSS] Apache Pulsar 2.7.1 Release

on an entry). We > > should include this in the 2.7.1 release. > > > > Thanks, > > Michael Marshall > > > > On Mon, Feb 22, 2021 at 2:01 AM Jinfeng Huang > > > > > wrote: > > > > > That's kind reminder, thank you Yong~ > >

Re: Publishing new version of Pulsar Build Docker image

we push the old image to docker hub ? > > In the meantime we can add the missing dependencies to the Dockerfile > > Enrico > > Il giorno mar 23 feb 2021 alle ore 08:42 Yong Zhang < > zhangyong1025...@gmail.com> ha scritto: > > > Looks like the new image brok

Re: Publishing new version of Pulsar Build Docker image

Looks like the new image broken the CPP build. I will try to use the old Dockerfile to build the "apache/pulsar/pulsar-build" image to make sure our CI back to normal. Here is the issue: https://github.com/apache/pulsar/issues/9682 On Tue, 23 Feb 2021 at 05:08, Ali Ahmed wrote: > I have pushed

Re: [DISCUSS] Apache Pulsar 2.7.1 Release

Thank you guys. I am clean up the PRs which are marked with the label `release/2.7.1`. If you have PR which marked the `release/2.7.1`, please take a look and make it merged as soon as possible, otherwise, it will be pushed into the next release. Thanks for your help! Yong Zhang On Mon, 22 Feb

Re: [DISCUSS] Apache pulsar-client-go v0.4.0 release

+1 good job！ Yong On Tue, 9 Feb 2021 at 15:59, xiaolong ran wrote: > Hello all: > > I will cut the 0.4.0 of go client, thanks everyone for this. > > -- > > Thanks > Xiaolong Ran > 在 2021年1月30日 +0800 PM3:10，xiaolong ran ，写道： > > Hello all: > > > > I hope you've all been doing well. Since the la

[DISCUSS] Apache Pulsar 2.7.1 Release

Hi all, I hope you've all been doing well. It has been two months since we released the Apache Pulsar 2.7.0. We have a lot of fixes already merged. So I would like to start to prepare our next patch release in the next few days. You can find the whole change list of the 2.7.1 release from: https

Re: [DISCUSS] Apache pulsar-client-go v0.4.0 release

+1 Best Yong On Sun, 31 Jan 2021 at 02:51, Sijie Guo wrote: > +1 > > On Sat, Jan 30, 2021 at 12:41 AM PengHui Li wrote: > > > +1 > > > > Thanks, > > Penghui > > > > xiaolong ran 于2021年1月30日周六 下午3:11写道： > > > > > Hello all: > > > > > > I hope you've all been doing well. Since the last v0.3.0 r

Re: Virtual Pulsar Community Meetings

Awesome. Agree with sijie, because of the timezone, it's better to run the meeting separately. Regards, Yong On Fri, 29 Jan 2021 at 16:53, Sijie Guo wrote: > That's a super great idea! Thank you for bringing this up! > > Given there are a lot of committers/contributors are from North America a

Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"

I am not sure that merge all the workflows into one workflow is a good idea. As I know, Github Actions doesn't allow to rerun a single job in a workflow. That means if there has any failure in the workflow, we need to rerun all steps/stage. There has a worst-case is we failed in the different test

Re: [Discuss] draft PIP for "Changes to flaky test handling"

Looking forward to the Pulsar test be more stable and CI can pass easily! -- Yong On Fri, 29 Jan 2021 at 00:35, Lari Hotari wrote: > Thank you Jennifer. I'll take a look soon. > Regards, Lari > > On Thu, Jan 28, 2021 at 4:13 PM Jinfeng Huang > > wrote: > > > Hi Lari, > > Thank you very much fo

Re: [ANNOUNCE] New committer: Yong Zhang

> > >> Congratulations! > > >> > > >> Best, > > >> Dianjin Wang > > >> > > >> On Fri, Jan 22, 2021 at 10:24 AM Jinfeng Huang > > >> wrote: > > >>> > > >>> Dear all, > > >>> The Apa

Re: [VOTE] Pulsar Release 2.7.0 Candidate 1

+1 (non-binding) - start standalone service - produce and consume messages - query the last message using pulsar-sql --- Yong On Wed, 25 Nov 2020 at 23:38, Sijie Guo wrote: > +1 (binding) > > - check signatures/checksums > - Validate Pub/Sub and Java Functions > - Validate Stateful Function

Re: Pulsar 2.7.0 and BooKeeper version

Yes! Sounds like it would make Pulsar more awesome! Regards, Yong On Mon, 2 Nov 2020 at 22:19, Jia Zhai wrote: > Thanks a lot for the initiative, Enrico. > From my point of view, It would be great if the upcoming Pulsar release > would have these features. > BP-41, and Explicit LAC would be a g

[DISCUSS] Introduce a cherry-pick command for cherry-picking PRs automatically

Hi developers, I want to introduce a command for cherry-picking PRs automatically. When we releasing a minor version of Pulsar, we need to cherry-pick the bug fix PRs into the release branch. Cherry-pick a lot of PRs will take a long time and sometimes there has some conflict need to resolve. I

[jira] [Created] (PULSAR-6) Add a new crowdin secret for publishing pulsar website

Yong Zhang created PULSAR-6: --- Summary: Add a new crowdin secret for publishing pulsar website Key: PULSAR-6 URL: https://issues.apache.org/jira/browse/PULSAR-6 Project: Pulsar Issue Type: Task

Re: [VOTE] Pulsar Client Go Release 0.2.0 Candidate 1

Great! +1 --- Yong On Wed, 26 Aug 2020 at 17:55, PengHui Li wrote: > +1 > > Thanks for driving this release! > Best Regards > > Penghui > On Aug 26, 2020, 2:41 PM +0800, Nozomi Kurihara , > wrote: > > +1 > > > > - verify shasum and asc > > - run producer and consumer > > > > Thanks for drivi

Re: [DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

Here is the vote thread: https://lists.apache.org/thread.html/r8254bb5756ea07d5156e1038c24684594993a8ad351b04a7d92c9276%40%3Cdev.pulsar.apache.org%3E - Yong On Fri, 19 Jun 2020 at 17:48, Yong Zhang wrote: > Sure. I will open an official vote for this. > > Thanks > - Yong > &

[VOTE] Accept Pulsarctl as part of Apache pulsar project

Hi all, I'd like to start a vote thread for accepting Pulsarctl[1] as part of Apache Pulsar project. Pulsarctl is an alternative tool of pulsar-admin, used to manage resources in Apache Pulsar. Please vote with your opinions. The vote will be open for at least 72 hours. [1] https://github.com/st

Re: [DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

> > - Sijie > > On Thu, Jun 18, 2020 at 9:13 PM Dave Fisher wrote: > > > Very cool! > > > > This contribution may need to go through IP clearance. > > https://incubator.apache.org/ip-clearance/ > > > > Regards? > > Dave > > > &g

Re: [DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

上午9:56写道： > > > Thanks Yong for this great job, +1 > > > > On 2020/6/15, 09:34, "PengHui Li" wrote: > > > > +1 > > On Jun 15, 2020, 9:24 AM +0800, xiaolong ran < > ranxiaolong...@gmail.com>, > > wrote: > > &g

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

+1 Thanks, Yong On Thu, 18 Jun 2020 at 11:15, Guangning E wrote: > +1 (non-binding) > > Thanks, > Guangning > > 丛搏 于2020年6月18日周四 上午11:09写道： > > > +1 (non-binding) > > > > > 2020年6月18日 上午11:02，PengHui Li 写道： > > > > > > +1 (binding) > > > > >

[DISCUSS] PIP-67: Contribute Pulsarctl to Apache Pulsar

Hi all, We have developed a new tool Pulsarctl for managing Pulsar resources. It’s written in Golang and is an alternative tool of pulsar-admin. We’d like to contribute the project back to the Pulsar community. ## Motivation Pulsarctl is an alternative tool of pulsar-admin, used to manage resour

Re: [VOTE] Pulsar Client Go Release 0.1.0 Candidate 1

+1 Thanks Yong On Thu, 26 Mar 2020 at 19:44, PengHui Li wrote: > +1 > > Sijie Guo 于2020年3月26日周四 上午8:28写道： > > > +1 > > > > On Tue, Mar 24, 2020 at 11:26 PM anonymitaet _ > > > wrote: > > > > > +1 > > > > > > Thanks xiaolong for your great work > > > > > > On 2020/3/25, 13:43, "xiaolong ran"

Re: [VOTE] Pulsar Release 2.5.0 Candidate 2

+1 (non-binding) - validate the checksum of the src, bin and connectors packages - compile the source code successfully - validate pub/sub and functions - validate connectors Regards, Yong On Mon, 6 Jan 2020 at 20:02, Sijie Guo wrote: > This is the second release candidate for Apache Pulsar, v

Re: [VOTE] Pulsar Release 2.5.0 Candidate 1

+1 (non-binding) - download the packages and verify the checksums - compile the source code successfully - produce and consume messages successfully - validate the functions and stateful functions Regards, Yong > On Dec 11, 2019, at 12:44 AM, Sijie Guo wrote: > > This is the first release cand

Re: [VOTE] Pulsar Release 2.4.2 Candidate 3

+1 (non-binding) Follow the release candidate validation validate checksums of the binary, source code and connector tarball compile the source code validate the pub and sub validate the state function validate the connector validate apache-rat check On Fri, 29 Nov 2019 at 15:41, xiaolong ran w

Re: [VOTE] Pulsar Release 2.4.2 Candidate 2

+1 (non-binding) follow the release candidate validation document - validate checksums of the binary, source code and connector tarball. - validate the pub and sub - validate the state function - validate the connector On Tue, 26 Nov 2019 at 14:06, xiaolong ran wrote: > Hi everyone, > > This is

Re: [VOTE] Pulsar Manager release 0.1.0 Candidate 4

+1 (non-binding) - check signatures and checksum - validate show tenant and namespace and topic I created Regards, Yong On Tue, 19 Nov 2019 at 14:18, Guangning E wrote: > Hi everyone, > Please review and vote on the release candidate #4 for the version 0.1.0, > as follows: > [ ] +1, Approve

Re: [REVOTE] PIP-47: Time Based Release Plan

+1 Thanks, Yong On Mon, Nov 11, 2019 at 11:45 Guangning E wrote: > +1 (non-binding) > > -- > Thanks, > Guangning > > xiaolong ran 于2019年11月11日周一 上午10:16写道： > > > Hello everyone: > > > > Please review and vote on the PIP-47 propose: > > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Bas

Re: [VOTE] PIP-47: Time Based Release Plan

+1 Thanks, Yong On Wed, 6 Nov 2019 at 18:37, Yuva raj wrote: > +1 non binding > > On Wed, 6 Nov 2019 at 11:18, xiaolong ran > wrote: > > > > Hi everyone > > > > Please review and vote on the PIP-47 propose, > > > > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan >

Re: [ DISCUSS ]PIP-50: Package Management

to make it > easier to extend to different protocol in the future. > > Thanks, > Sijie > > On Thu, Oct 31, 2019 at 5:03 PM Yong Zhang > wrote: > > > Hi all, > > > > I am starting a proposal about providing a package management to manage > > use

[ DISCUSS ]PIP-50: Package Management

Hi all, I am starting a proposal about providing a package management to manage user functions and connectors. *motivation* Apache Pulsar provides Functions for users transforming their data as they want. If there are many users who use the same function in different namespaces, they need to up

Pulsar go admin client and pulsarctl

Hi Pulsar community, We just open sourced a Pulsar go admin client library and a CLI tool `pulsarctl` built on top of it. If you are writing Golong applications to interact with Pulsar, definitely check this out! https://github.com/streamnative/pulsarctl pulsarctl command reference: https://

Re: Enable Wiki tab for pulsar-manager repository

+1 On Fri, 25 Oct 2019 at 17:21, Guangning E wrote: > Hi, everyone > > Currently, I'm trying to document the release procedure for pulsar-manager. > I want to use GitHub Wiki for that, but the Wiki tab for the pulsar-manager > repository is disabled now. > https://github.com/apache/pulsar-manage

Re: Jenkins migration proposal

Hi all, The GitHub Actions works well on the public repo. Also can verify the pull request from the fork. To test the Github Actions, I create a public repo and use an account without the GitHub Actions service to create a pull request. The GitHub Actions working well. I think we can consider

Re: [VOTE] Pulsar Release 2.4.1 Candidate 1

+1 Follow the Release-Candidate-Validation - check the binary distribution - table service starts well - function worker is started correctly - sanity check looks well - create tenant/namespace/function worked - produce/consume messages worked - connector worked - stateful functions worked - go c

Re: Jenkins migration proposal

Hi all, I found the Github Actions only can running on the base repository. If I create a pull request from fork repo, it will not be running. FYI: https://github.community/t5/GitHub-API-Development-and/Run-a-GitHub-action-on-pull-request-for-PR-opened-from-a-forked/m-p/15426#M363 On Tue, 27 Au

Re: [VOTE] Pulsar Release 2.4.0 Candidate 2

Hi all, +1 Follow the validation guide: https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Verified: 1. Pulsar standalone 2. Create tenant and namespace 3. Create function 4. Publish and consume message 5. Stateful Functions Best regard! On Wed, 26 Jun 2019 at 19:15, PengHui

Re: [VOTE] Pulsar Release 2.4.0 Candidate 1

Hi all, +1 Follow the validation guide: https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Verified: 1. Pulsar standalone 2. Create tenant and namespace 3. Create function 4. Publish and consume message 5. Stateful Functions Best regard! Yong On Sun, 23 Jun 2019 at 13:16,

Re: [VOTE] Pulsar Release 2.3.2 Candidate 1

+1 Environment: MacOS 10.14.4 I followed this https://github.com/apache/pulsar/wiki/Release-Candidate-Validation checked: * Start standalone service * pub/sub message * connectors On Fri, 24 May 2019 at 00:33, Matteo Merli wrote: > +1 > > Environment: MacOS 10.14 > > Checked: > * Signatures >

Re: PIP 36: Max message size

t; Thanks Yong for the PIP. > > > > I moved your gist to Pulsar wiki page: > > https://github.com/apache/pulsar/wiki/PIP-36%3A-Max-Message-Size > > > > The proposal looks good to me. +1 > > > > - Sijie > > > > On Mon, May 6, 2019 at 6:04 PM Yong

PIP 36: Max message size

hi all, Currently `MaxMessageSize` is hardcoded in Pulsar and it can’t be modified in server configuration. So there is no way when user want to modify the limit to transfer larger size message. Hence i propose adding a `MaxMessageSize` config in `broker.conf` to solve this problem. Because brok

Re: [VOTE] Pulsar Release 2.3.1 Candidate 2

+1 on release candidate I followed the validation guide https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Verified : 1. Pub/Sub and Java Functions 2. Connectors 3. Stateful Functions On Fri, 12 Apr 2019 at 00:35, Ivan Kelly wrote: > Hi folks, > > +1 from me (binding) > > ✓