Re: [VOTE] PIP-257: Add Open ID Connect Support to Server Components
+1 (binding) Sent from my iPhone > On Mar 27, 2023, at 12:59 PM, Lari Hotari wrote: > > +1, binding > > -Lari > >> On Mon, 27 Mar 2023, 22.37 Michael Marshall, wrote: >> >> Hi Pulsar Community, >> >> This thread is to start the vote for PIP 257. >> >> Discussion: >> https://lists.apache.org/thread/ttdh74t6v5nznmtw436otk8qdymjvrfk >> Issue: https://github.com/apache/pulsar/issues/19771 >> Work in Progress Implementations: >> - https://github.com/apache/pulsar/pull/19849 >> - https://github.com/apache/pulsar/pull/19888 >> >> The implementation still has some minor details to iron out, but I >> don't think those are a large enough issue to delay the vote any >> longer. If you feel otherwise, please let me know and continue the >> discussion on the discussion thread. >> >> Thanks, >> Michael >>
Re: [DISCUSS] forbid user to upload `BYTES` schema
Hi yufan. Can you describe a bit the usage scenario of byte schema in flink-connector-pulsa? Thanks, sinan Yufan Sheng 于 2023年3月28日周二 上午9:53写道： > As the flink-connector-pulsar developer, I don't want to disable the > BYTES schema upload. In my opinion, using BYTES schema means the users > want to bypass the schema check and handle the schema validation by > themselves. > > On Tue, Mar 28, 2023 at 8:58 AM SiNan Liu wrote: > > > > Hi, everyone. > > When a user uploads bytes schema. We can warn the user and skip uploading > > bytes schema. > > Also check to see if the topic has a schema other than bytes. > > 1. If yes, warn the user that it is not necessary to upload bytes schema. > > You can subscribe to a topic using bytes schema. > > 2. If there is no schema, warn the user that the topic does not have a > > schema. The default is bytes schema, and there is no need to upload it. > > Rather than simply throwing an exception rejecting the upload bytes > schema. > > > > > > Thanks, > > sinan > > > > > > Christophe Bornet 于 2023年3月28日周二 上午1:15写道： > > > > > This change broke the Flink SQL Pulsar connector: > > > https://github.com/streamnative/flink/issues/270 > > > So I propose to revert it. > > > > > > Le ven. 9 déc. 2022 à 11:57, labuladong a > écrit : > > > > > > > > Hi pulsar community, > > > > > > > > > > > > I'd like to discuss the behavior of schema uploading, for more > context > > > see https://github.com/apache/pulsar/issues/18825 > > > > > > > > > > > > I think that forbidding users to upload `BYTES` schema is a > recommended > > > way to solve this issue. But this may change the existing behavior, so > do > > > you have any suggestion about this issue? > > > > > > > > > > > > Thanks, > > > > Donglai > > > >
Re: [VOTE] Pulsar Release 2.9.5 Candidate 1
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: > 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 *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.5-candidate-1/ > > SHA-512 checksums: > cd4e1d57db29e4e06f2bf9d036741785b10905d924a3d6a33e2de472bcf2032b3451451efa9d2fed5acffd9534edffb3189e2f90cdc8f58f523bd8288d067381 > apache-pulsar-2.9.5-bin.tar.gz > 293b2a094a62f08223b6c7367f55fb75f79910c23cd24c96fccf71cc6deeb10707825a1b45cbece34788f0a7f3bf65996c9b6c0a4fd1fdd575cedd4828fa4e85d44 > apache-pulsar-2.9.5-src.tar.gz > 294654ad51084c04bcfa35e07555ec628a187824538f328651d00294f4ec459898ca2506f720ecc6d29994abfd85424bd734f4b4c6dc57276223e9d51068be9 > apache-pulsar-offloaders-2.9.5-bin.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1219/ > > The tag to be voted upon: > v2.9.5-candidate-1 (4322b70ccb6a17ca8d43cc60aaa02d9c86a23cd5) > https://github.com/apache/pulsar/releases/tag/v2.9.5-candidate-1 > > Pulsar's KEYS file containing PGP keys you use to sign the release: > https://downloads.apache.org/pulsar/KEYS > > Docker images: > > > https://hub.docker.com/layers/czcoder/pulsar/2.9.5/images/sha256-ff679eafaf46ec94ee211bb185e81e9767df04f4ab8ca420fc1271eab7aca8cd?context=explore > > > https://hub.docker.com/layers/czcoder/pulsar-all/2.9.5/images/sha256-e29c4b9076e56ce11067564c12de8da993ceb5986084c868488ab7c71483286e?context=explore > > > https://hub.docker.com/layers/czcoder/pulsar-grafana/2.9.5/images/sha256-8d34754e5192937570bfd839d7395d80a1492b5eda8dcd0a35dffddfef30b772?context=explore > > Please download the source package, and follow the README to build > and run the Pulsar standalone service. >
Re: [DISCUSS] forbid user to upload `BYTES` schema
As the flink-connector-pulsar developer, I don't want to disable the BYTES schema upload. In my opinion, using BYTES schema means the users want to bypass the schema check and handle the schema validation by themselves. On Tue, Mar 28, 2023 at 8:58 AM SiNan Liu wrote: > > Hi, everyone. > When a user uploads bytes schema. We can warn the user and skip uploading > bytes schema. > Also check to see if the topic has a schema other than bytes. > 1. If yes, warn the user that it is not necessary to upload bytes schema. > You can subscribe to a topic using bytes schema. > 2. If there is no schema, warn the user that the topic does not have a > schema. The default is bytes schema, and there is no need to upload it. > Rather than simply throwing an exception rejecting the upload bytes schema. > > > Thanks, > sinan > > > Christophe Bornet 于 2023年3月28日周二 上午1:15写道： > > > This change broke the Flink SQL Pulsar connector: > > https://github.com/streamnative/flink/issues/270 > > So I propose to revert it. > > > > Le ven. 9 déc. 2022 à 11:57, labuladong a écrit : > > > > > > Hi pulsar community, > > > > > > > > > I'd like to discuss the behavior of schema uploading, for more context > > see https://github.com/apache/pulsar/issues/18825 > > > > > > > > > I think that forbidding users to upload `BYTES` schema is a recommended > > way to solve this issue. But this may change the existing behavior, so do > > you have any suggestion about this issue? > > > > > > > > > Thanks, > > > Donglai > >
Re: [DISCUSS] forbid user to upload `BYTES` schema
Hi, everyone. When a user uploads bytes schema. We can warn the user and skip uploading bytes schema. Also check to see if the topic has a schema other than bytes. 1. If yes, warn the user that it is not necessary to upload bytes schema. You can subscribe to a topic using bytes schema. 2. If there is no schema, warn the user that the topic does not have a schema. The default is bytes schema, and there is no need to upload it. Rather than simply throwing an exception rejecting the upload bytes schema. Thanks, sinan Christophe Bornet 于 2023年3月28日周二 上午1:15写道： > This change broke the Flink SQL Pulsar connector: > https://github.com/streamnative/flink/issues/270 > So I propose to revert it. > > Le ven. 9 déc. 2022 à 11:57, labuladong a écrit : > > > > Hi pulsar community, > > > > > > I'd like to discuss the behavior of schema uploading, for more context > see https://github.com/apache/pulsar/issues/18825 > > > > > > I think that forbidding users to upload `BYTES` schema is a recommended > way to solve this issue. But this may change the existing behavior, so do > you have any suggestion about this issue? > > > > > > Thanks, > > Donglai >
Re: [VOTE] PIP-257: Add Open ID Connect Support to Server Components
+1, binding -Lari On Mon, 27 Mar 2023, 22.37 Michael Marshall, wrote: > Hi Pulsar Community, > > This thread is to start the vote for PIP 257. > > Discussion: > https://lists.apache.org/thread/ttdh74t6v5nznmtw436otk8qdymjvrfk > Issue: https://github.com/apache/pulsar/issues/19771 > Work in Progress Implementations: > - https://github.com/apache/pulsar/pull/19849 > - https://github.com/apache/pulsar/pull/19888 > > The implementation still has some minor details to iron out, but I > don't think those are a large enough issue to delay the vote any > longer. If you feel otherwise, please let me know and continue the > discussion on the discussion thread. > > Thanks, > Michael >
[VOTE] PIP-257: Add Open ID Connect Support to Server Components
Hi Pulsar Community, This thread is to start the vote for PIP 257. Discussion: https://lists.apache.org/thread/ttdh74t6v5nznmtw436otk8qdymjvrfk Issue: https://github.com/apache/pulsar/issues/19771 Work in Progress Implementations: - https://github.com/apache/pulsar/pull/19849 - https://github.com/apache/pulsar/pull/19888 The implementation still has some minor details to iron out, but I don't think those are a large enough issue to delay the vote any longer. If you feel otherwise, please let me know and continue the discussion on the discussion thread. Thanks, Michael
Re: [DISCUSS] PIP-257: Add Open ID Connect Support to Server Components
Here is the K8s integration: https://github.com/apache/pulsar/pull/19888. That PR makes it possible to configure a function running in kubernetes to use the Service Account Token provided by kubernetes. Future work suggested by Eron Wright is to add support for the function worker to mount tokens for any requested audience. I think that feature will be very valuable, but in hopes of completing this PIP by 3.0.0, I would like to defer that feature. Thanks, Michael On Mon, Mar 20, 2023 at 5:59 PM Michael Marshall wrote: > > Update: the PR [0] to add the OIDC authentication provider module is > ready for review. > > I plan to start looking at the function worker integration with k8s tomorrow. > > I hope to start the vote later this week. > > Thanks, > Michael > > [0] https://github.com/apache/pulsar/pull/19849 > > On Mon, Mar 20, 2023 at 5:56 PM Michael Marshall wrote: > > > > >> 2. Implement `KubernetesFunctionAuthProvider` with > > >`KubernetesSecretsAuthProvider`. > > > > >It looks like we add an authentication provider for the Kubernetes > > >environment. Is the OIDC authentication provider? > > > > The current KubernetesSecretsTokenAuthProvider [0] mounts the auth > > data used to create a function. Because OIDC often has short lived > > tokens, it won't work to copy the token from the call used to create > > the function. Instead, my initial proposal was to let a user specify a > > pre-existing k8s secret that will have the correct authentication > > data. Because anything can be in the secret, there isn't a reason to > > require this secret to have the client id and client secret. > > > > Eron suggested in the PIP issue [1] that we make it possible to easily > > integrate with the Kubernetes Service Account. I'll be looking into > > that integration this week. > > > > Thanks, > > Michael > > > > [0] > > https://github.com/apache/pulsar/blob/82237d3684fe506bcb6426b3b23f413422e6e4fb/pulsar-functions/runtime/src/main/java/org/apache/pulsar/functions/auth/KubernetesSecretsTokenAuthProvider.java > > [1] https://github.com/apache/pulsar/issues/19771#issuecomment-1463029346 > > > > > > On Mon, Mar 13, 2023 at 3:03 AM Zixuan Liu wrote: > > > > > > Hi Michael, > > > > > > +1, Thank you for your PIP! That's important for modern authentication! > > > > > > I have a question: > > > > > > > 2. Implement `KubernetesFunctionAuthProvider` with > > > `KubernetesSecretsAuthProvider`. > > > > > > It looks like we add an authentication provider for the Kubernetes > > > environment. Is the OIDC authentication provider? > > > > > > > > > Thanks, > > > Zixuan > > > > > > > > > > > > Lari Hotari 于2023年3月10日周五 14:56写道： > > > > > > > Thanks for starting this PIP, Michael. > > > > This is really important in improving Pulsar's security and reducing > > > > certain attack surfaces and eliminating certain attack vectors. I'm > > > > looking > > > > forward to having Open ID connect (OIDC) supported in Pulsar server > > > > components so that Pulsar could be operated without the use of static > > > > JWT > > > > tokens such as the superuser token. > > > > > > > > -Lari > > > > > > > > On 2023/03/09 22:34:49 Michael Marshall wrote: > > > > > Hi Pulsar Community, > > > > > > > > > > I would like to contribute Open ID Connect support to the server > > > > > components in Pulsar. Here is a link to the PIP: > > > > > https://github.com/apache/pulsar/issues/19771. I plan to start working > > > > > on the implementation next week. I look forward to your feedback. > > > > > > > > > > Thanks, > > > > > Michael > > > > > > > > > > ### Motivation > > > > > > > > > > Apache Pulsar does not yet support a server side > > > > > `AuthenticationProvider` that implements the Open ID Connect spec for > > > > > a relying party as defined by https://openid.net/connect/. The only > > > > > token based authentication is provided via the > > > > > `AuthenticationProviderToken` class. Given that we already have > > > > > clients that implement the OAuth2.0 protocol, which integrates easily > > > > > with an Open ID Connect `AuthenticationProvider`, it would be very > > > > > helpful to add this support to the Pulsar Server components. > > > > > > > > > > ### Goal > > > > > > > > > > In implementing the OIDC spec, we will fulfill both the core > > > > > (https://openid.net/specs/openid-connect-core-1_0.html) and the > > > > > discovery (https://openid.net/specs/openid-connect-discovery-1_0.html) > > > > > portions of the spec in the `AuthenticationProvider` implementation. > > > > > > > > > > The end result will be a plugin that: > > > > > > > > > > * supports multiple token issuers > > > > > > > > > > * retrieves the JWKS uri for each issuer from the token issuer's > > > > > `/.well-known/openid-configuration` endpoint > > > > > > > > > > * retrieves and caches the JKWS when a client attempts to connect > > > > > using a token issued by one of the trusted issuers > > > > > > > > > > * refreshes the JWKS after a configured amount of time, which
Re: [DISCUSS] forbid user to upload `BYTES` schema
This change broke the Flink SQL Pulsar connector: https://github.com/streamnative/flink/issues/270 So I propose to revert it. Le ven. 9 déc. 2022 à 11:57, labuladong a écrit : > > Hi pulsar community, > > > I'd like to discuss the behavior of schema uploading, for more context see > https://github.com/apache/pulsar/issues/18825 > > > I think that forbidding users to upload `BYTES` schema is a recommended way > to solve this issue. But this may change the existing behavior, so do you > have any suggestion about this issue? > > > Thanks, > Donglai
[VOTE] Pulsar Release 2.9.5 Candidate 2
This is the third release candidate for Apache Pulsar, version 2.9.5. This release contains 103 commits by 30 contributors. https://github.com/apache/pulsar/compare/v2.9.4...v2.9.5-candidate-2 *** Please download, test, and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag), binaries are provided for convenience. Source and binary files: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.9.5-candidate-2/ SHA-512 checksums: 5e1d0c1b38441cdcb36a2f4e59ab9755b39a5c4a0136e078e91ab9bc2169016f195268692cafd6f13a45248dba2e97959b41f3cfbc8659e3cbd0bade0c954998 apache-pulsar-2.9.5-bin.tar.gz 72c9f47005636c6e629dd5117b15fdc13bfd9c7efe107be77a9d55b7dfcdda2f941003eb120ea8beeffe44c41bc41c385a2e5a9cb6540d2fe83a6d04ea53a7389d apache-pulsar-2.9.5-src.tar.gz 73d286af64e189cf91c0511d360d98371b7ade1eec67bc6acf6ff766784e9e40388d3da8ae99a206369feaf398b254fff36e2206077041c37b8055ee7edde86eea apache-pulsar-offloaders-2.9.5-bin.tar.gz Maven staging repo: https://repository.apache.org/content/repositories/orgapachepulsar-1222/ The tag to be voted upon: v2.9.5-candidate-2 (c75c811ee48f51cf74f399f5b364bc1527186b34) https://github.com/apache/pulsar/releases/tag/v2.9.5-candidate-2 Pulsar's KEYS file containing PGP keys you use to sign the release: https://downloads.apache.org/pulsar/KEYS Docker images: https://hub.docker.com/layers/czcoder/pulsar/2.9.5/images/sha256-c6d3435d5699cb3697ee2ddc4f8a45e0ac5e35d8aefd557e280b7cf91366b981?context=explore https://hub.docker.com/layers/czcoder/pulsar-all/2.9.5/images/sha256-a09a8e177ca7856c29dc8b9828cd293c6d44b473add20d1877bb3137b94a20c5?context=explore https://hub.docker.com/layers/czcoder/pulsar-grafana/2.9.5/images/sha256-c43a489c65cf6c407d6c3be6fc7a001227805b1aaa9413115cf55ba11a1e329f?context=explore Please download the source package, and follow the README to build and run the Pulsar standalone service. Thanks Cong Zhao
Re: [VOTE] Pulsar Client Go Release 0.10.0 Candidate 1
+1(non-binding) - Checked the signature - Verify producer, consumer, and reader examples on README. Thanks, Baodi Shi 在 2023年3月27日 20:23:28 上，Zike Yang 写道： > Hi everyone, > Please review and vote on the release candidate #1 for the version > 0.10.0, as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the first release candidate for Apache Pulsar Go client, version > 0.10.0. > > It fixes the following issues: > https://github.com/apache/pulsar-client-go/milestone/12?closed=1 > > Pulsar Client Go's KEYS file contains PGP keys we used to sign this > release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Please download these packages and review this release candidate: > - Review release notes: > https://github.com/apache/pulsar-client-go/pull/997 > - Download the source package (verify shasum, and asc) and follow the > README.md to build and run the pulsar-client-go. > > The vote will be open for at least 72 hours. It is adopted by majority > approval, with at least 3 PMC affirmative votes. > > Source file: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.10.0-candidate-1/ > > The tag to be voted upon: > v0.10.0 > https://github.com/apache/pulsar-client-go/tree/v0.10.0-candidate-1 > > SHA-512 checksums: > > 5f26d95061eb535595043ffc23424d9913f11d1b80ca815bdd20577453f6e08c2a5dd8b729d82494c4f5d0260905b231218c6a437995d893c4c25efdb0bb > apache-pulsar-client-go-0.10.0-src.tar.gz > > Zike Yang >
Re: PIP-214 has been proceeded without consensus
Hi Asaf, > Shouldn’t poeople that has write access to merge must first validate of course if PIP is approved before merge? Yeah. I think they should have to. Now we have two issues here: 1. Since the patch is merged, I send a notice here so that if anyone objects this proposal, they can raise a revert request. 2. Validate our process and notify committers to verify PRs associated with PIP that the proposal is approved. Maybe the author can help set the PR as a draft before the PIP reached a consensus also. Best, tison. Asaf Mesika 于2023年3月27日周一 20:48写道： > I don’t a role in Pulsar. > I reviewed the code and it was altered until it was satisfactory. > > Shouldn’t poeople that has write access to merge must first validate of > course if PIP is approved before merge? > > > > On 26 Mar 2023, at 15:27, tison wrote: > > > > Hi, > > > > I noticed that PIP-214[1] "Add broker level metrics statistics and expose > > to prometheus" was discussed at [2], but we didn't start a vote. However, > > the patch and doc updates were merged [3][4]. > > > > When trying to close the issue, I found this case, and I'm wondering if > > it's not a proposal or we do something wrong here. > > > > Best, > > tison. > > > > [1] https://github.com/apache/pulsar/issues/18056 > > [2] https://lists.apache.org/thread/0qcwntm7hoc9x21dn21ybnq9qo5ogqsw > > [3] https://github.com/apache/pulsar/pull/19047 > > [4] https://github.com/apache/pulsar-site/pull/475 > >
[VOTE] Pulsar Client Go Release 0.10.0 Candidate 1
Hi everyone, Please review and vote on the release candidate #1 for the version 0.10.0, as follows: [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) This is the first release candidate for Apache Pulsar Go client, version 0.10.0. It fixes the following issues: https://github.com/apache/pulsar-client-go/milestone/12?closed=1 Pulsar Client Go's KEYS file contains PGP keys we used to sign this release: https://dist.apache.org/repos/dist/dev/pulsar/KEYS Please download these packages and review this release candidate: - Review release notes: https://github.com/apache/pulsar-client-go/pull/997 - Download the source package (verify shasum, and asc) and follow the README.md to build and run the pulsar-client-go. The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Source file: https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-go-0.10.0-candidate-1/ The tag to be voted upon: v0.10.0 https://github.com/apache/pulsar-client-go/tree/v0.10.0-candidate-1 SHA-512 checksums: 5f26d95061eb535595043ffc23424d9913f11d1b80ca815bdd20577453f6e08c2a5dd8b729d82494c4f5d0260905b231218c6a437995d893c4c25efdb0bb apache-pulsar-client-go-0.10.0-src.tar.gz Zike Yang
Re: [VOTE] Pulsar Release 2.11.1 Candidate-1
+1 (binding) system: mac os 12.6, Apple M1 maven: 3.8.5 java: OpenJDK 17.0.3 - Checked the signature - Checked LICENSE - Start standalone with zookeeper stream storage - Publish and consume messages - Verified Function and State Function - Verified Cassandra connector - Build from the source package - Run a simple transaction check Thanks, Bo Yunze Xu 于2023年3月27日周一 12:01写道： > > +1 (binding) > > - Checked the signature > - Build from source (Java 17, Ubuntu 20.04 WSL2) > - Start standalone with both RocksDB and ZooKeeper > - Run basic end-to-end Pulsar tests and topic operations via pulsar-shell > - Run basic end-to-end Kafka tests with KoP 2.11.0.4 > > Thanks, > Yunze > > On Wed, Mar 22, 2023 at 4:51 PM guo jiwei wrote: > > > > This is the first release candidate for Apache Pulsar, version 2.11.1. > > > > This release contains 188 commits by 53 contributors. > > https://github.com/apache/pulsar/compare/v2.11.0...v2.11.1-candidate-1 > > > > CI for this release candidate > > https://github.com/Technoboy-/pulsar/pull/28 > > > > *** Please download, test and vote on this release. This vote will stay open > > for at least 72 hours *** > > > > Note that we are voting upon the source (tag), binaries are provided for > > convenience. > > > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.11.1-candidate-1 > > > > SHA-512 checksums: > > > > 7bd5c432fdb888dfcc2a1595efe29206545db535ea996aa4d1ff851e957cc88ce4b54fce912dde84baf8ed40217149a0acffad6c49f02f348721350e5ae895dd > > > > ./apache-pulsar-2.11.1-bin.tar.gz > > > > > > 9e7bfac98e57a2a61216da77e48843bc4274828c9da1e695538d92a3ee929b52c4b0d2280feb73980d77f02c03f3c2dbc797673e69df19190ffee8e46760f305 > > > > ./apache-pulsar-2.11.1-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1220/ > > > > The tag to be voted upon: > > v2.11.1-candidate-1 (7cc41d7dec415acfeb1f96b68faaa2a80440e070) > > https://github.com/apache/pulsar/releases/tag/v2.11.1-candidate-1 > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > https://hub.docker.com/layers/mattison/pulsar-all/2.11.1-rc1/images/sha256-3d2c0bacbc6d34fa656466370744dedfd2b5a79df7a1178ea2fad27a6d6a > > > > https://hub.docker.com/layers/mattison/pulsar/2.11.1-rc1/images/sha256-1fda65d5637ad579ee36ab09448eb6ff3831583a9ef5b543bae78a565813cd95 > > > > Please download the source package, and follow the > > release-candidate-validation doc to build > > and run the Pulsar standalone service. > > https://pulsar.apache.org/contribute/validate-release-candidate > > > > Since the metadata store is changed from ZK to RocksDB, the > > verification of the `stateful functions` needs to set the parameter > > "export PULSAR_STANDALONE_USE_ZOOKEEPER=1" > > > > > > Regards > > Jiwei Guo (Tboy)
Re: [VOTE] Pulsar Release 2.10.4 Candidate 3
+1(binding) Please ignore the previous reply, I read it wrong, sorry. +1 (binding) os: mac 12.3.1, Intel java: OpenJDK 17.0.1 - Checked the signature - Checked LICENSE - Start standalone - Publish and consume messages - Verified Function and State Function - Verified Cassandra connector - Build from the source package (maven 3.8.6, openJDK 11.0.12) - Run a simple transaction check Thanks, Bo 丛搏 于2023年3月27日周一 18:20写道： > > Hi, Xiangying: > > I found in > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.4-candidate-3/connectors/ > has two pulsar-io-debezium-mssql-2.10.4.nar > > Thanks, > Bo > > guo jiwei 于2023年3月23日周四 18:27写道： > > > > +1 (binding) > > > > - Checked the signature > > - Checked LICENSE > > - Publish and consume messages > > - Verified Function and State Function > > - Verified Cassandra connector > > - Build from the source package > > > > > > Regards > > Jiwei Guo (Tboy) > > > > On Wed, Mar 22, 2023 at 3:08 PM Xiangying Meng wrote: > > > > > > This is the third release candidate for Apache Pulsar, version 2.10.4. > > > > > > This release contains 111 commits by 35 contributors. > > > https://github.com/apache/pulsar/compare/v2.10.3...v2.10.4-candidate-3 > > > > > > *** Please download, test and vote on this release. This vote will stay > > > open > > > for at least 72 hours *** > > > > > > Note that we are voting upon the source (tag), binaries are provided for > > > convenience. > > > > > > Source and binary files: > > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.4-candidate-3/ > > > > > > SHA-512 checksums: > > > 59f0326643cca9ef16b45b4b522ab5a1c1d8dc32ac19897704f8231f9bd4cef02af722848646332db461a807daacc9cb87993b81dcf1429b1f23e3872a32 > > > apache-pulsar-2.10.4-bin.tar.gz > > > 5b2adbf0d371b79b1dbe141f152848049d19924151fa8827057038d81833accd70cf67429cb003aedb8d44ee705ed0609d49757e74fed377dce77b09d49062e3 > > > apache-pulsar-2.10.4-src.tar.gz > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachepulsar-1221/ > > > > > > The tag to be voted upon: > > > v2.10.4-candidate-3 > > > (e4898ac8eb37f698f29aa21e40a3abdda5489d45) > > > https://github.com/apache/pulsar/releases/tag/v2.10.4-candidate-3 > > > > > > Pulsar's KEYS file containing PGP keys you use to sign the release: > > > https://downloads.apache.org/pulsar/KEYS > > > > > > Docker images: > > > > > > > > > https://hub.docker.com/layers/xiangyingmeng/pulsar/2.10.4/images/sha256-05bfb482c5b5aa66ac818651d8997745ac7d536ca0cb56bff8199a6de459ac45?context=repo > > > > > > > > > https://hub.docker.com/layers/xiangyingmeng/pulsar-all/2.10.4/images/sha256-d4f3de64a8ec4a9039ac500bbf4a0efae9a9f1d4e0a58e11cab020276dc5e6b3?context=repo > > > > > > Please download the source package, and follow the README to build > > > and run the Pulsar standalone service.
Re: Re: Re: Introducer Pulsar admin api to pulsar-client-go
Hi, Enrico, Thanks for your concerns. I suppose we'll initiate the PIP discussion thread soon. Welcome to keep following the current repo https://github.com/streamnative/pulsar-admin-go. Best, Max Xu On Mon, Mar 27, 2023 at 3:09 PM Enrico Olivelli wrote: > Eric, > > Il Lun 27 Mar 2023, 07:44 Shen Eric ha > scritto: > > > Hi Community, > > > > We want to announce and introduce the [Pulsar Admin Go Library]( > > https://github.com/streamnative/pulsar-admin-go) which has been open > > sourced and cut the first release. > > > > The original Pulsar Admin Go Library is from [pulsarctl]( > > https://github.com/streamnative/pulsarctl)'s internal pkg which is not > > convenient for Pulsar Golang developers to use and manage. So, we > decoupled > > the Pulsar Admin related API from pulsarctl and created the > > [pulsar-admin-go](https://github.com/streamnative/pulsar-admin-go) > > library based on it, which also provides a clearer perspective and > > maintainability from an architectural perspective. > > > > In the future plan of this library: > > - Iterate the library and upgrade the related admin API based on the > > Pulsar progress. > > - More testing and dogfood from StreamNative’s golang projects: > > [pulsarctl](https://github.com/streamnative/pulsarctl), > > [terraform-provider-pulsar]( > > https://github.com/streamnative/terraform-provider-pulsar), > > [pulsar-resources-operator]( > > https://github.com/streamnative/pulsar-resources-operator). > > - When the library is stable, will donate it to Apache Foundation. > > > > Thanks for sharing the progress. > > I think that it is better to move the API to the Apache repository and then > we can improve it all together as a community. > It is fine if it is not 100% perfect yet, don't worry about that. > > > Cheers > Enrico > > > > > > -- > > > > Best regards, > > > > Eric Shen > > > > On 2023/03/17 09:09:38 Max Xu wrote: > > > Thanks Yu and Eric for your follow-up. > > > > > > Yes, we're working on that. I believe we will soon see pulsar-admin-go > :) > > > > > > > > > Best, > > > Max Xu > > > > > > > > > On Wed, Mar 15, 2023 at 2:36 PM Yu wrote: > > > > > > > Hi Eric, > > > > > > > > Thanks for sharing the updates! > > > > > > > > I discussed this project with Max previously. We would like to > > contribute > > > > docs for it, and I've already added "Go admin API (coming soon)" to > > the new > > > > Pulsar API docs already [1], which brings many benefits, such as: > > > > > > > > - Build excitement before launch. > > > > - Generate a targeted list of early adopters interested in this > > brand-new > > > > tool. > > > > - Improve SEO by adding relevant keywords. > > > > > > > > [1] > > https://github.com/apache/pulsar-site/pull/462#discussion_r1130770643 > > > > > > > > Yu > > > > > > > > > > > > On Wed, Mar 15, 2023 at 11:56 AM Shen Eric > > > > wrote: > > > > > > > > > Hi Zhangjian, > > > > > > > > > > We can share some progress on our side: > > > > > > > > > > we have completed: > > > > > > > > > > * Extracted the pulsar-admin-go library from the pulsarctl and > moved > > > > > it to a separate repo under StreamNative (now it is private) > > > > > * Updated the project layout and rename some pkg names like the cli > > > > pkg > > > > > > > > > > what we will do next: > > > > > > > > > > * Add some pulsar-admin-go library documentation > > > > > * Setup some CI/CD infra configurations for the repo > > > > > * Then we will release the 0.1.0 and open source this repo > > > > > > > > > > The release of the 0.1.0 and repo open-source we wanna make it in > > March > > > > > and will announce this to the community. > > > > > > > > > > The timeline to donate this project to Apache is undecided now but > we > > > > will > > > > > listen to the feedback from the community and donate it when most > of > > us > > > > > think it's qualified and stable. > > > > > > > > > > On 2023/03/03 04:14:33 ZhangJian He wrote: > > > > > > Hi, Eric. Thank you very much for the work you have done. I have > no > > > > > > objections to the process, and it would be even better if there > > could > > > > be > > > > > a > > > > > > rough timeline. > > > > > > > > > > > > Thanks > > > > > > ZhangJian He > > > > > > > > > > > > > > > > > > On Fri, 3 Mar 2023 at 09:06, Shen Eric > wrote: > > > > > > > > > > > > > Hi Zhangjian, > > > > > > > > > > > > > > I am a PM from StreamNative and we also had some internal > > discussions > > > > > > > related to this topic. Let me share our ongoing planning: > > > > > > > > > > > > > > * We will extract the pulsar admin pkg from the pulsarctl to a > > > > > > > separate open repo which will be called pulsar-admin-go under > > > > > StreamNative. > > > > > > > * Will iterate the pulsar-admin-go library by adding more > tests, > > > > > > > documentation and may also update or fix the existing APIs. > > > > > > > * After the pulsar-admin-go library is stable, we will > contribute > > > > this > > > > > > > project to Apache Foundation. > > >
Re: [VOTE] Pulsar Release 2.10.4 Candidate 3
Hi, Xiangying: I found in https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.4-candidate-3/connectors/ has two pulsar-io-debezium-mssql-2.10.4.nar Thanks, Bo guo jiwei 于2023年3月23日周四 18:27写道： > > +1 (binding) > > - Checked the signature > - Checked LICENSE > - Publish and consume messages > - Verified Function and State Function > - Verified Cassandra connector > - Build from the source package > > > Regards > Jiwei Guo (Tboy) > > On Wed, Mar 22, 2023 at 3:08 PM Xiangying Meng wrote: > > > > This is the third release candidate for Apache Pulsar, version 2.10.4. > > > > This release contains 111 commits by 35 contributors. > > https://github.com/apache/pulsar/compare/v2.10.3...v2.10.4-candidate-3 > > > > *** Please download, test and vote on this release. This vote will stay open > > for at least 72 hours *** > > > > Note that we are voting upon the source (tag), binaries are provided for > > convenience. > > > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-2.10.4-candidate-3/ > > > > SHA-512 checksums: > > 59f0326643cca9ef16b45b4b522ab5a1c1d8dc32ac19897704f8231f9bd4cef02af722848646332db461a807daacc9cb87993b81dcf1429b1f23e3872a32 > > apache-pulsar-2.10.4-bin.tar.gz > > 5b2adbf0d371b79b1dbe141f152848049d19924151fa8827057038d81833accd70cf67429cb003aedb8d44ee705ed0609d49757e74fed377dce77b09d49062e3 > > apache-pulsar-2.10.4-src.tar.gz > > > > Maven staging repo: > > https://repository.apache.org/content/repositories/orgapachepulsar-1221/ > > > > The tag to be voted upon: > > v2.10.4-candidate-3 > > (e4898ac8eb37f698f29aa21e40a3abdda5489d45) > > https://github.com/apache/pulsar/releases/tag/v2.10.4-candidate-3 > > > > Pulsar's KEYS file containing PGP keys you use to sign the release: > > https://downloads.apache.org/pulsar/KEYS > > > > Docker images: > > > > > > https://hub.docker.com/layers/xiangyingmeng/pulsar/2.10.4/images/sha256-05bfb482c5b5aa66ac818651d8997745ac7d536ca0cb56bff8199a6de459ac45?context=repo > > > > > > https://hub.docker.com/layers/xiangyingmeng/pulsar-all/2.10.4/images/sha256-d4f3de64a8ec4a9039ac500bbf4a0efae9a9f1d4e0a58e11cab020276dc5e6b3?context=repo > > > > Please download the source package, and follow the README to build > > and run the Pulsar standalone service.
Re: [VOTE] PIP-254: Support configuring client version with a description suffix
+1 Thanks, Lin Lin 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/apache/pulsar/issues/19705 > > Thanks, > Yunze >
Re: [VOTE] PIP-254: Support configuring client version with a description suffix
+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/apache/pulsar/issues/19705 > > Thanks, > Yunze >
Re: Re: Re: Introducer Pulsar admin api to pulsar-client-go
Eric, Il Lun 27 Mar 2023, 07:44 Shen Eric ha scritto: > Hi Community, > > We want to announce and introduce the [Pulsar Admin Go Library]( > https://github.com/streamnative/pulsar-admin-go) which has been open > sourced and cut the first release. > > The original Pulsar Admin Go Library is from [pulsarctl]( > https://github.com/streamnative/pulsarctl)'s internal pkg which is not > convenient for Pulsar Golang developers to use and manage. So, we decoupled > the Pulsar Admin related API from pulsarctl and created the > [pulsar-admin-go](https://github.com/streamnative/pulsar-admin-go) > library based on it, which also provides a clearer perspective and > maintainability from an architectural perspective. > > In the future plan of this library: > - Iterate the library and upgrade the related admin API based on the > Pulsar progress. > - More testing and dogfood from StreamNative’s golang projects: > [pulsarctl](https://github.com/streamnative/pulsarctl), > [terraform-provider-pulsar]( > https://github.com/streamnative/terraform-provider-pulsar), > [pulsar-resources-operator]( > https://github.com/streamnative/pulsar-resources-operator). > - When the library is stable, will donate it to Apache Foundation. > Thanks for sharing the progress. I think that it is better to move the API to the Apache repository and then we can improve it all together as a community. It is fine if it is not 100% perfect yet, don't worry about that. Cheers Enrico > > -- > > Best regards, > > Eric Shen > > On 2023/03/17 09:09:38 Max Xu wrote: > > Thanks Yu and Eric for your follow-up. > > > > Yes, we're working on that. I believe we will soon see pulsar-admin-go :) > > > > > > Best, > > Max Xu > > > > > > On Wed, Mar 15, 2023 at 2:36 PM Yu wrote: > > > > > Hi Eric, > > > > > > Thanks for sharing the updates! > > > > > > I discussed this project with Max previously. We would like to > contribute > > > docs for it, and I've already added "Go admin API (coming soon)" to > the new > > > Pulsar API docs already [1], which brings many benefits, such as: > > > > > > - Build excitement before launch. > > > - Generate a targeted list of early adopters interested in this > brand-new > > > tool. > > > - Improve SEO by adding relevant keywords. > > > > > > [1] > https://github.com/apache/pulsar-site/pull/462#discussion_r1130770643 > > > > > > Yu > > > > > > > > > On Wed, Mar 15, 2023 at 11:56 AM Shen Eric > > > wrote: > > > > > > > Hi Zhangjian, > > > > > > > > We can share some progress on our side: > > > > > > > > we have completed: > > > > > > > > * Extracted the pulsar-admin-go library from the pulsarctl and moved > > > > it to a separate repo under StreamNative (now it is private) > > > > * Updated the project layout and rename some pkg names like the cli > > > pkg > > > > > > > > what we will do next: > > > > > > > > * Add some pulsar-admin-go library documentation > > > > * Setup some CI/CD infra configurations for the repo > > > > * Then we will release the 0.1.0 and open source this repo > > > > > > > > The release of the 0.1.0 and repo open-source we wanna make it in > March > > > > and will announce this to the community. > > > > > > > > The timeline to donate this project to Apache is undecided now but we > > > will > > > > listen to the feedback from the community and donate it when most of > us > > > > think it's qualified and stable. > > > > > > > > On 2023/03/03 04:14:33 ZhangJian He wrote: > > > > > Hi, Eric. Thank you very much for the work you have done. I have no > > > > > objections to the process, and it would be even better if there > could > > > be > > > > a > > > > > rough timeline. > > > > > > > > > > Thanks > > > > > ZhangJian He > > > > > > > > > > > > > > > On Fri, 3 Mar 2023 at 09:06, Shen Eric wrote: > > > > > > > > > > > Hi Zhangjian, > > > > > > > > > > > > I am a PM from StreamNative and we also had some internal > discussions > > > > > > related to this topic. Let me share our ongoing planning: > > > > > > > > > > > > * We will extract the pulsar admin pkg from the pulsarctl to a > > > > > > separate open repo which will be called pulsar-admin-go under > > > > StreamNative. > > > > > > * Will iterate the pulsar-admin-go library by adding more tests, > > > > > > documentation and may also update or fix the existing APIs. > > > > > > * After the pulsar-admin-go library is stable, we will contribute > > > this > > > > > > project to Apache Foundation. > > > > > > > > > > > > Do you think this plan works for you? > > > > > > > > > > > > On 2023/02/17 01:47:26 ZhangJian He wrote: > > > > > > > I would like to express that the current Pulsar client for Go > > > > > > > (pulsar-client-go) is missing the pulsar Admin API. As such, I > > > would > > > > like > > > > > > > to propose that we work towards adding this feature to > > > > pulsar-client-go. > > > > > > > > > > > > > > I believe that this new feature would be a valuable addition to > > > > > > > pulsar-client-go, and I am excited to work to make it
