[GitHub] [pulsar-dotpulsar] blankensteiner commented on pull request #110: modified the "hello world" to fix first run issue
blankensteiner commented on PR #110: URL: https://github.com/apache/pulsar-dotpulsar/pull/110#issuecomment-1263140651 Hi @aintJoshinya Thanks for the PR! I agree with the minimal optional configuration, but setting the initial position is the right solution and one I find people missing, so it could be wise to show it in that example. It will ensure that it works no matter how you arrange the code. If you can change the fix to set the initial position, I will be happy to merge the PR :-) -- 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. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar] Anonymitaet added a comment to the discussion: [Design] Pulsar All Releases Page
GitHub user Anonymitaet added a comment to the discussion: [Design] Pulsar All Releases Page Hi @eolivelli, We have an issue with 2.9.0 and 2.9.1 and find that you're the release manager for them. Could you please give us a hand? Thank you! 🔹🔹🔹 ### Context We (@urfreespace, @SignorMercurio) are implementing this idea. The [Pulsar release table](https://pulsar.apache.org/release-notes/) is automatically generated based on the info of the [Pulsar GitHub release page](https://github.com/apache/pulsar/releases), where 2.9.0 and 2.9.1 are missing. We're wondering why and figuring out how to deal with this situation. https://user-images.githubusercontent.com/50226895/193180574-94ec2c19-ad76-46ed-b5e8-83bbea6a1d58.png";> ### Questions - 2.9.0: from the [2.9.0 release note](https://pulsar.staged.apache.org/release-notes/#290), we know it's a special release. Is this the reason for not showing 2.9.0 on the [Pulsar GitHub release page](https://github.com/apache/pulsar/releases)? https://user-images.githubusercontent.com/50226895/193181694-dbe77820-a99c-4083-9665-e494378bca97.png";> - 2.9.1: from the [2.9.1 release note](https://pulsar.staged.apache.org/release-notes/#291), seems that this is a correct release. Then why is 2.9.1 missing on the [Pulsar GitHub release page](https://github.com/apache/pulsar/releases)? Should it be added? GitHub link: https://github.com/apache/pulsar/discussions/17310#discussioncomment-3768488 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
[GitHub] [pulsar] raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level.
GitHub user raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level. We are using broker (server) version `2.8` and pulsar-client version on the java application `2.10.0 ` GitHub link: https://github.com/apache/pulsar/discussions/17626#discussioncomment-3768364 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
Re: [DISCUSS] Use AUTO_CONSUME schema with Avro logical type conversion problem
Bo, Il giorno lun 26 set 2022 alle ore 15:39 丛搏 ha scritto: > > Hello, Pulsar community: > > Now, we use Avro Schema with Logical type, and the client > automatically adds logical type conversion. You can see PR > https://github.com/apache/pulsar/pull/6704. > > But AUTO_CONSUME Schema with Avro doesn't add the logical type > conversion. It makes the Time type decode to Long. > We have two ways to solve the problem: > 1. Added configuration control whether to add. This doesn't bring > compatibility issues. > 2. Do not add configuration to control, add directly like Avro Schema. > It will bring compatibility issues > > I prefer option 2 because it is a bug in itself. We don't need to > consider compatibility. Otherwise, schema loses its meaning. There is already a NATIVE_AVRO schema, you can use a native Avro schema. The problem is that it doesn't do the AUTO_CONSUME() magic that downloads the schema. We could add some configuration to AUTO_CONSUME() like AUTO_CONSUME(Consumer nativeSchemaCustomizer) that is still in the direction that we took in 2.8 to encourage users to access native objects instead of using the pulsar GenericRecord API, that is too high level and cannot cover specific features of AVRO, Jackson, Protobuf... By the way, even if we let people customize the Schema instance in their programs, we still have the problem with Pulsar Functions and with Pulsar Sinks. If you encode with your custom Schema, you must consume the data with the same customisations. I don't have a solution for the problem at the moment Enrico > > What do you think, leave your opinion :) > > Thanks > Bo,
Re: [VOTE] Pulsar Client Go Release 0.9.0 Candidate 2
+1 (binding) - build from the source code - test the produce and consume Penghui On Thu, Sep 29, 2022 at 2:43 PM Guangning E wrote: > +1(non-binding) > - Check sha 512 value for source code > - Check go build producer example > > Thanks, > Guangning > > r...@apache.org 于2022年9月29日周四 14:35写道： > > > Hi everyone, > > > > Please review and vote on the release candidate #2 for the version 0.9.0, > > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > This is the second release candidate for Apache Pulsar Go client, > > version 0.9.0. > > > > It fixes the following issues: > > https://github.com/apache/pulsar-client-go/milestone/10?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/804 > > - 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.9.0-candidate-2/ > > > > The tag to be voted upon: > > v0.9.0 > > > https://github.com/apache/pulsar-client-go/releases/tag/v0.9.0-candidate-2 > > > > SHA-512 checksums: > > > > > 9731d6a0615288e77feb4b73fedbbdf6d275ebefeee3cee5fc4e849f38789863f0532c7e8b93eb1e601bd98f9bb21d50a714fcf87fac9987a745a052bbe23ca3 > > apache-pulsar-client-go-0.9.0-candidate-2-src.tar.gz > > > > Best, > > > > Xiaolong Ran > > >
Re: [DISCUSS] Changed pulsar-go-client minimum Go SDK version from 1.15 to 1.16
+1 Passing the git ID and other version information via ldflags would be better in my opinion than embedding a file. It can be automated in the Makefile, and the values can go directly into a variable, so you don't have to do any string parsing. The feature has been around a long time, so we wouldn't need to increase the minimum Go version. On Thu, Sep 29, 2022 at 8:43 AM Ming Luo wrote: > Have you thought about using ldflags to pass git commit or git tag which > can be the actual version. This will tie into a build system automatically > without additional files. We don't have to maintain the version > information in git and a separate file. > Here is an example. > > https://urldefense.com/v3/__https://stackoverflow.com/questions/11354518/application-auto-build-versioning/55090713*55090713__;Iw!!PbtH5S7Ebw!eR_uHNK3r-klu3s2SdSgZYyQ6vW7X2-gTWTxxFK-RzPj5G23CJbZyVTU4SJa4M8WEAc0rns0tm6aXT1eTEgWQlc-JZ8wSCs$ > > > On Thu, 29 Sept 2022 at 02:41, r...@apache.org > wrote: > > > Hello Matteo: > > > > Considering that some users are still using the Go 1.15 version, in the > > 0.9.0 release, we still use the form of hard code and set the form of > > pulsar-go-client to the version of 0.9.0. In order to ensure that the > 0.9.0 > > release maintains backward compatibility, we may continue to do this for > a > > while. When we scrap Go 1.15, we will use the official Go embed to > > dynamically configure pulsar Version information for -client-go. > > > > -- > > Thanks > > Xiaolong Ran > > > > Matteo Merli 于2022年9月29日周四 11:33写道： > > > > > +1 > > > > > > It would be good to determine and document a compatibility policy to > > state > > > which versions are going to be supported and for how long. > > > > > > On Wed, Sep 28, 2022 at 8:31 PM 沈家琦 wrote: > > > > > > > +1 > > > > pulsar-go-client from Go 1.15 to Go 1.16 > > > > > > > > Thanks > > > > > > > > r...@apache.org 于2022年9月29日周四 11:11写道： > > > > > > > > > Hello everyone: > > > > > > > > > > In the current version of pulsar-go-client, we do not support > > embedding > > > > the > > > > > version information of pulsar-go-client into > > > > > Client Command to send to the Broker. Now the hard code is fixed to > > > > 0.1.0. > > > > > This makes it impossible for us to determine > > > > > which version of pulsar-go-client the current user is using through > > the > > > > > version information. > > > > > > > > > > To support this feature, the more clumsy method is described using > > > > > https://github.com/apache/pulsar-client-go/pull/820. > > > > > However, Go 1.16 officially supports the feature of embed ( > > > > > > https://urldefense.com/v3/__https://pkg.go.dev/embed__;!!PbtH5S7Ebw!eR_uHNK3r-klu3s2SdSgZYyQ6vW7X2-gTWTxxFK-RzPj5G23CJbZyVTU4SJa4M8WEAc0rns0tm6aXT1eTEgWQlc-3UTCMWo$ > ), which supports reading the > > > > > specified file directly, which seems to be a more elegant way, but > > this > > > > > requires Go 1.16 version. Yes, the current minimum > > > > > version supported by our pulsar-go-client is Go 1.15, which > requires > > us > > > > to > > > > > change the minimum version of > > > > > pulsar-go-client from Go 1.15 to Go 1.16. > > > > > > > > > > So here we start a discussion within the community to see if we can > > > make > > > > > this change. > > > > > > > > > > -- > > > > > Thanks > > > > > Xiaolong Ran > > > > > > > > > > > > -- > > > -- > > > Matteo Merli > > > > > > > > > > > -- > Powered by Pulsar > Engineering, Kesque >
Re: [DISCUSS] Changed pulsar-go-client minimum Go SDK version from 1.15 to 1.16
Have you thought about using ldflags to pass git commit or git tag which can be the actual version. This will tie into a build system automatically without additional files. We don't have to maintain the version information in git and a separate file. Here is an example. https://stackoverflow.com/questions/11354518/application-auto-build-versioning/55090713#55090713 On Thu, 29 Sept 2022 at 02:41, r...@apache.org wrote: > Hello Matteo: > > Considering that some users are still using the Go 1.15 version, in the > 0.9.0 release, we still use the form of hard code and set the form of > pulsar-go-client to the version of 0.9.0. In order to ensure that the 0.9.0 > release maintains backward compatibility, we may continue to do this for a > while. When we scrap Go 1.15, we will use the official Go embed to > dynamically configure pulsar Version information for -client-go. > > -- > Thanks > Xiaolong Ran > > Matteo Merli 于2022年9月29日周四 11:33写道： > > > +1 > > > > It would be good to determine and document a compatibility policy to > state > > which versions are going to be supported and for how long. > > > > On Wed, Sep 28, 2022 at 8:31 PM 沈家琦 wrote: > > > > > +1 > > > pulsar-go-client from Go 1.15 to Go 1.16 > > > > > > Thanks > > > > > > r...@apache.org 于2022年9月29日周四 11:11写道： > > > > > > > Hello everyone: > > > > > > > > In the current version of pulsar-go-client, we do not support > embedding > > > the > > > > version information of pulsar-go-client into > > > > Client Command to send to the Broker. Now the hard code is fixed to > > > 0.1.0. > > > > This makes it impossible for us to determine > > > > which version of pulsar-go-client the current user is using through > the > > > > version information. > > > > > > > > To support this feature, the more clumsy method is described using > > > > https://github.com/apache/pulsar-client-go/pull/820. > > > > However, Go 1.16 officially supports the feature of embed ( > > > > https://pkg.go.dev/embed), which supports reading the > > > > specified file directly, which seems to be a more elegant way, but > this > > > > requires Go 1.16 version. Yes, the current minimum > > > > version supported by our pulsar-go-client is Go 1.15, which requires > us > > > to > > > > change the minimum version of > > > > pulsar-go-client from Go 1.15 to Go 1.16. > > > > > > > > So here we start a discussion within the community to see if we can > > make > > > > this change. > > > > > > > > -- > > > > Thanks > > > > Xiaolong Ran > > > > > > > > > -- > > -- > > Matteo Merli > > > > > -- Powered by Pulsar Engineering, Kesque
Re: Pulsar CI slowness continues
Il giorno mer 28 set 2022 alle ore 07:50 Lari Hotari ha scritto: > > There was an incident with GitHub Actions yesterday, > https://www.githubstatus.com/incidents/nbhb2lxyh9bb . > > It looks like Pulsar CI is back in action today. > > I finally got a helpful response from GitHub Support. They are now aware of > the issues and looking for ways how to improve the situation for Apache > organization projects. Great news ! Enrico > > > -Lari > > On 2022/09/27 16:01:41 Lari Hotari wrote: > > Hi all, > > > > GitHub Actions isn't providing sufficient resources for apache/pulsar > > repository at the moment and this causes the build queue to increase. > > > > We are already using the solution where most of the builds are run in the > > context of the forked repository. This remains currently the only practical > > way to get CI feedback and it has been working well. > > > > Here are the Pulsar CI instructions for running Pulsar CI tests in your own > > fork of apache/pulsar after you have created a PR to apache/pulsar. The > > benefit of this solution is that your own fork has independent quota from > > apache/pulsar and this is usually not congested. All Apache projects share > > the same quota on GitHub and that's one reason why apache/pulsar is > > suffering from insufficient GitHub Actions resources. > > > > 1. Go to your fork of apache/pulsar in the GitHub UI and ensure that your > > master branch is up to date with https://github.com/apache/pulsar. Sync > > your fork if it's behind. > >- > > https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork > > 2. Open a pull request to your own fork for the pull request branch. If the > > apache/pulsar CI jobs run, it will provide a link which can be used to > > create the pull request conveniently. This link is in the build failure > > message. > > 3. Edit the description of the upstream pull request made to apache/pulsar > > repository and add the link to the PR that you opened to your own fork so > > that the reviewer can verify that tests pass in your own fork. > > 4. Ensure that tests pass in your own fork. Your own fork will be used to > > run the tests during the PR review and any changes made during the review. > > You as a PR author are responsible for following up on test failures. > > - Please report any flaky tests as new issues at > > https://github.com/apache/pulsar/issues after checking that the flaky test > > isn't already reported. > > 5. When the PR is approved, it will be possible to restart the Pulsar CI > > workflow within apache/pulsar repository by adding a comment "/pulsarbot > > rerun-failure-checks" to the PR. > > An alternative for the PR approval is to add a ready-to-test label to the > > PR. This can be done by Apache Pulsar committers. > > 6. When tests pass on the apache/pulsar side, the PR can be merged by a > > Apache Pulsar Committer. > > > > At the moment, there's a long build queue and it takes very long to get any > > builds started for apache/pulsar builds. If this situation continues, we > > might have to considers an approach where we drop the "required checks" > > requirement for apache/pulsar and solely trust on the results of test runs > > made in the forked repostories. It's not an optimal solution since it's > > possible that some PRs get accidentially merged when the test status in the > > fork isn't properly validated by the committer who merges the PR. This > > solution would allow us to keep on processing PRs while there's a resource > > shortage in GitHub Actions for the Apache organization account. > > I have an issue opened to GitHub support, but the support engineer hasn't > > provided sufficient answer and resolution yet. I don't have high hopes > > about it being helpful since GitHub support hasn't been very responsive and > > supportive in resolving the matter. > > > > Best Regards, > > > > -Lari > >
Re: Master branch is broken due to #15914
> I think that we should be able (committers, or at least PMC members) > to push changes without passing for CI. Otherwise it may be sometimes > impossible to fix or revert. I guess that in this case, we don't need to by-pass CI. If we ever have to do that, it is possible by first editing .asf.yaml and removing "required_status_checks" for the master branch. After that change is merged, it's possible to merge without running CI. If CI is completely unavailable or broken, ASF INFRA jira ticket can be used for asking an admin to disable required status checks manually for the apache/pulsar repository. -Lari On Thu, Sep 29, 2022 at 2:06 PM Enrico Olivelli wrote: > > Hello, > I have to revert this patch > https://github.com/apache/pulsar/pull/15914 because now many tests > fail > > > This is the revert PR > https://github.com/apache/pulsar/pull/17889 > > I think that we should be able (committers, or at least PMC members) > to push changes without passing for CI. Otherwise it may be sometimes > impossible to fix or revert. > > Please anyone approve and merge the PR > > Best regards > Enrico
[GitHub] [pulsar] Jason918 added a comment to the discussion: Need max redelivery count at message level.
GitHub user Jason918 added a comment to the discussion: Need max redelivery count at message level. This issue is not verified on the latest pulsar version. Which pulsar version are you using? GitHub link: https://github.com/apache/pulsar/discussions/17626#discussioncomment-3761863 This is an automatically sent email for dev@pulsar.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
Master branch is broken due to #15914
Hello, I have to revert this patch https://github.com/apache/pulsar/pull/15914 because now many tests fail This is the revert PR https://github.com/apache/pulsar/pull/17889 I think that we should be able (committers, or at least PMC members) to push changes without passing for CI. Otherwise it may be sometimes impossible to fix or revert. Please anyone approve and merge the PR Best regards Enrico
[GitHub] [pulsar] raunakagrawal47 added a comment to the discussion: Need max redelivery count at message level.
GitHub user raunakagrawal47 added a comment to the discussion: Need max
redelivery count at message level.
@Jason918 @michaeljmarshall facing below issue:
https://github.com/apache/pulsar/issues/12021
I am trying to produce 10 messages at a time. And all these 10 messages should
be getting retried 'x' number of times by 1 consumer. ('x' varies at message
level). But it errors out and is not able to retry.
The error message says: `Need Non-Null value for key`. How can we resolve it?
GitHub link:
https://github.com/apache/pulsar/discussions/17626#discussioncomment-3761020
This is an automatically sent email for dev@pulsar.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@pulsar.apache.org
Re: [VOTE] Pulsar Release 2.10.2 Candidate 1
+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 > - Signatures/Digests > - Built on Mac, using JDK 11 Temurin > - Verified LICENSE files (using the script), both on the staged > tarball and on the tarbal produced by building from source > - Did a couple of smoke tests on Pulsar standalone, from the binary package > > Thanks for driving the release Haiting > > Enrico > > Il giorno gio 29 set 2022 alle ore 09:47 r...@apache.org > ha scritto: > > > > +1 (non-binding) > > > > - Checksum and signatures > > - Run Go SDK produce/consume > > - Run Pulsar standalone and produce/consume case > > > > -- > > Thanks > > Xiaolong Ran > > > > guo jiwei 于2022年9月29日周四 11:30写道： > > > > > +1 (binding) > > > > > > - Checksum and signatures > > > - Apache Rat check passes > > > - Compile from source with JDK11 > > > - Validate Pub/Sub and Java functions > > > - Validate Connectors > > > - Validate Stateful functions > > > > > > Regards > > > Jiwei Guo (Tboy) > > > > > > > > > On Thu, Sep 29, 2022 at 12:26 AM Nicolò Boschi > > > wrote: > > > > > > > +1 (non binding) > > > > > > > > > > > > - Checksum and signatures > > > > > > > > - Apache Rat check passes > > > > > > > > - Compile from source w JDK11 > > > > > > > > - Build docker image from source > > > > > > > > - Run Pulsar standalone and produce-consume from CLI > > > > > > > > - Tested a couple of connectors (ElasticSink, JDBC sink) in K8S env > > > > > > > > Nicolò Boschi > > > > > > > > > > > > Il giorno lun 26 set 2022 alle ore 13:42 Haiting Jiang < > > > > jianghait...@gmail.com> ha scritto: > > > > > > > > > This is the first release candidate for Apache Pulsar, version > 2.10.2. > > > > > > > > > > This release contains 244 commits by 57 contributors. > > > > > > https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-1 > > > > > > > > > > Full CI on this release: > > > > > https://github.com/Jason918/pulsar/pull/8 > > > > > > > > > > *** 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.2-candidate-1/ > > > > > > > > > > SHA-512 checksums: > > > > > > > > > > > > > > > > > > fc7ed1947bf737b92ab097dc0eb500567668a6f64ed6e88af9d1f5bf9c266f77e50d3ea28944856f39afb0140232747693d61836b99eb22b7580e8a6cad4ce7d > > > > > ./apache-pulsar-2.10.2-bin.tar.gz > > > > > > > > > > > > > > > > > > cab39ab5c24e2d01074d9169b641cdb80a59609462b664f6892905d6e995a72b02ab48cc8456cf90883a810af6085465cc8371df5e498bc1e13700ad0864d6af > > > > > ./apache-pulsar-2.10.2-src.tar.gz > > > > > > > > > > Maven staging repo: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1179/ > > > > > > > > > > The tag to be voted upon: > > > > > v2.10.2-candidate-1 (ddd642e77deacc42ad2542df39cbb22ef5217b25) > > > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-1 > > > > > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > > > > > Docker images: > > > > > > > > > > > > > > > > > > https://hub.docker.com/layers/jason918/pulsar/2.10.2/images/sha256-2a6543a6f6b40af34760418ff199a771f91d85539e2cac692a524f3056d2226e > > > > > > > > > > > > > > > > > > https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-f9dc9b9ce224c69ab3616e7b3bbceafcb27504c81c791e2410115454a48c7837 > > > > > > > > > > Please download the source package, and follow the > > > > > release-candidate-validation doc to build > > > > > and run the Pulsar standalone service. > > > > > > > > > > > > > > > > > > https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md > > > > > > > > > > Thanks, > > > > > Haiting > > > > > > > > > > > > >
Re: [VOTE] Pulsar Release 2.10.2 Candidate 1
+1 (binding) - Apache RAT - Signatures/Digests - Built on Mac, using JDK 11 Temurin - Verified LICENSE files (using the script), both on the staged tarball and on the tarbal produced by building from source - Did a couple of smoke tests on Pulsar standalone, from the binary package Thanks for driving the release Haiting Enrico Il giorno gio 29 set 2022 alle ore 09:47 r...@apache.org ha scritto: > > +1 (non-binding) > > - Checksum and signatures > - Run Go SDK produce/consume > - Run Pulsar standalone and produce/consume case > > -- > Thanks > Xiaolong Ran > > guo jiwei 于2022年9月29日周四 11:30写道： > > > +1 (binding) > > > > - Checksum and signatures > > - Apache Rat check passes > > - Compile from source with JDK11 > > - Validate Pub/Sub and Java functions > > - Validate Connectors > > - Validate Stateful functions > > > > Regards > > Jiwei Guo (Tboy) > > > > > > On Thu, Sep 29, 2022 at 12:26 AM Nicolò Boschi > > wrote: > > > > > +1 (non binding) > > > > > > > > > - Checksum and signatures > > > > > > - Apache Rat check passes > > > > > > - Compile from source w JDK11 > > > > > > - Build docker image from source > > > > > > - Run Pulsar standalone and produce-consume from CLI > > > > > > - Tested a couple of connectors (ElasticSink, JDBC sink) in K8S env > > > > > > Nicolò Boschi > > > > > > > > > Il giorno lun 26 set 2022 alle ore 13:42 Haiting Jiang < > > > jianghait...@gmail.com> ha scritto: > > > > > > > This is the first release candidate for Apache Pulsar, version 2.10.2. > > > > > > > > This release contains 244 commits by 57 contributors. > > > > https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-1 > > > > > > > > Full CI on this release: > > > > https://github.com/Jason918/pulsar/pull/8 > > > > > > > > *** 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.2-candidate-1/ > > > > > > > > SHA-512 checksums: > > > > > > > > > > > > > fc7ed1947bf737b92ab097dc0eb500567668a6f64ed6e88af9d1f5bf9c266f77e50d3ea28944856f39afb0140232747693d61836b99eb22b7580e8a6cad4ce7d > > > > ./apache-pulsar-2.10.2-bin.tar.gz > > > > > > > > > > > > > cab39ab5c24e2d01074d9169b641cdb80a59609462b664f6892905d6e995a72b02ab48cc8456cf90883a810af6085465cc8371df5e498bc1e13700ad0864d6af > > > > ./apache-pulsar-2.10.2-src.tar.gz > > > > > > > > Maven staging repo: > > > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1179/ > > > > > > > > The tag to be voted upon: > > > > v2.10.2-candidate-1 (ddd642e77deacc42ad2542df39cbb22ef5217b25) > > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-1 > > > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > > > Docker images: > > > > > > > > > > > > > https://hub.docker.com/layers/jason918/pulsar/2.10.2/images/sha256-2a6543a6f6b40af34760418ff199a771f91d85539e2cac692a524f3056d2226e > > > > > > > > > > > > > https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-f9dc9b9ce224c69ab3616e7b3bbceafcb27504c81c791e2410115454a48c7837 > > > > > > > > Please download the source package, and follow the > > > > release-candidate-validation doc to build > > > > and run the Pulsar standalone service. > > > > > > > > > > > > > https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md > > > > > > > > Thanks, > > > > Haiting > > > > > > > > >
Re: [VOTE] Pulsar Release 2.10.2 Candidate 1
+1 (non-binding) - Checksum and signatures - Run Go SDK produce/consume - Run Pulsar standalone and produce/consume case -- Thanks Xiaolong Ran guo jiwei 于2022年9月29日周四 11:30写道： > +1 (binding) > > - Checksum and signatures > - Apache Rat check passes > - Compile from source with JDK11 > - Validate Pub/Sub and Java functions > - Validate Connectors > - Validate Stateful functions > > Regards > Jiwei Guo (Tboy) > > > On Thu, Sep 29, 2022 at 12:26 AM Nicolò Boschi > wrote: > > > +1 (non binding) > > > > > > - Checksum and signatures > > > > - Apache Rat check passes > > > > - Compile from source w JDK11 > > > > - Build docker image from source > > > > - Run Pulsar standalone and produce-consume from CLI > > > > - Tested a couple of connectors (ElasticSink, JDBC sink) in K8S env > > > > Nicolò Boschi > > > > > > Il giorno lun 26 set 2022 alle ore 13:42 Haiting Jiang < > > jianghait...@gmail.com> ha scritto: > > > > > This is the first release candidate for Apache Pulsar, version 2.10.2. > > > > > > This release contains 244 commits by 57 contributors. > > > https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-1 > > > > > > Full CI on this release: > > > https://github.com/Jason918/pulsar/pull/8 > > > > > > *** 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.2-candidate-1/ > > > > > > SHA-512 checksums: > > > > > > > > > fc7ed1947bf737b92ab097dc0eb500567668a6f64ed6e88af9d1f5bf9c266f77e50d3ea28944856f39afb0140232747693d61836b99eb22b7580e8a6cad4ce7d > > > ./apache-pulsar-2.10.2-bin.tar.gz > > > > > > > > > cab39ab5c24e2d01074d9169b641cdb80a59609462b664f6892905d6e995a72b02ab48cc8456cf90883a810af6085465cc8371df5e498bc1e13700ad0864d6af > > > ./apache-pulsar-2.10.2-src.tar.gz > > > > > > Maven staging repo: > > > > https://repository.apache.org/content/repositories/orgapachepulsar-1179/ > > > > > > The tag to be voted upon: > > > v2.10.2-candidate-1 (ddd642e77deacc42ad2542df39cbb22ef5217b25) > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-1 > > > > > > Pulsar's KEYS file containing PGP keys we use to sign the release: > > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > > > > > Docker images: > > > > > > > > > https://hub.docker.com/layers/jason918/pulsar/2.10.2/images/sha256-2a6543a6f6b40af34760418ff199a771f91d85539e2cac692a524f3056d2226e > > > > > > > > > https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-f9dc9b9ce224c69ab3616e7b3bbceafcb27504c81c791e2410115454a48c7837 > > > > > > Please download the source package, and follow the > > > release-candidate-validation doc to build > > > and run the Pulsar standalone service. > > > > > > > > > https://github.com/apache/pulsar/blob/master/wiki/release/release-candidate-validation.md > > > > > > Thanks, > > > Haiting > > > > > >
