Re: [VOTE] Pulsar Release 2.6.4 Candidate 1

+1 (non-binding) - validate pub/sub and java/go functions - validate connectors - validate stateful functions - validate go client pub/sub -- Thanks Xiaolong Ran Lari Hotari 于2021年5月28日周五 下午6:12写道： > This is the first release candidate for Apache Pulsar, version 2.6.4. > > It contains the fol

Re: [ANNOUNCE] New committer: Yunze Xu

Congrats to Yunze, --- Thanks Xiaolong Ran Jia Zhai 于2021年5月31日周一 上午11:56写道： > Hi everyone, > > The Project Management Committee (PMC) for Apache Pulsar has invited > Yunze Xu (https://github.com/BewareMyPower ) > to > become a committer and we > are pleased to annou

[GitHub] [pulsar-client-node] massakam merged pull request #159: Fix Leak in MessageId::ToString

massakam merged pull request #159: URL: https://github.com/apache/pulsar-client-node/pull/159 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this servi

Re: [VOTE] Pulsar Release 2.6.4 Candidate 1

+1 (non binding) Build from sources Run Internal System tests with Fallout Thank you Lari for driving the release Enrico Il giorno mar 1 giu 2021 alle ore 09:28 r...@apache.org ha scritto: > > +1 (non-binding) > > - validate pub/sub and java/go functions > - validate connectors > - validate sta

Re: [DISCUSS] Propose More Formal Policy for Security Patches and EOL of Versions

LGTM +1 PIP-47 itself also has this scenario consideration. We can quickly iterate through small versions to quickly respond to problems that may occur in each major version, and we can submit patches for major versions at any time. -- Thanks Xiaolong Ran Michael Marshall 于2021年5月28日周五 上午5:4

Re: [VOTE] Pulsar Release 2.6.4 Candidate 1

+1 (non-binding) * checkout tag v2.6.4-candidate-1 and build from source code * start standalone server and run pub-sub tests * deploy on internal pulsar test cluster and run internal tests. Thank you Lari for driving the release. Thanks, Hang Enrico Olivelli 于2021年6月1日周二 下午3:51写道：

Standardize authentication and authorization terms

The Pulsar code base uses different terms (principal, role, client-id, app-id, etc..) when referring to authentication and authorization. Different places use different terms that may or may not mean the same thing. All these different terms get overloaded and make it confusing to reason about the

Re: Updates on Presto connector for PIP-62

Actually we're in the process of contributing the Trino(formerly PrestoSQL) connector back to Trino repo. I'm not sure if we still want to maintain the connector in the Pulsar repo after that? It's just gonna be super hard to maintain 2 copies of the code and porting patch between them, and most li

Re: Standardize authentication and authorization terms

Hello Chris: This is a good idea. If possible, you can submit a PIP to list the confusion of the current terminology and if we want to unify, do we need to make some changes to the current structure? In this case, it is convenient for us to further evaluate whether the current idea can be better