[DISCUSS] Update schema authentication permission issue
Hello, Pulsar community: Now, we have two authentications for updating the schema 1. producer and consumer can update the schema using TopicOperation produce or consume when open autoUpdateSchema 2. pulsar admin uses Tenant authentication This will produce problems when using different authentications to update the schema. There are two solutions here: 1. use produce authentication, small changes, and compatibility with the original mode. But it's not clear and not flexible enough 2. add single update schema authentication in TopicOperation. Big changes, not compatible with the original mode, but more clear and flexible I prefer to use the produce authentication because it doesn't affect the existing authentication policy. I hope you can discuss and provide your own views Thanks, Bo
[GitHub] [pulsar] goncalocribeiro added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency
GitHub user goncalocribeiro added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency Unfortunately no. I didn't find anything useful GitHub link: https://github.com/apache/pulsar/discussions/17988#discussioncomment-3862680 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] michaeljmarshall added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency
GitHub user michaeljmarshall added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency Glad you found something that worked. When you enable debug logs, do you get any helpful messages to understand where it is stuck? GitHub link: https://github.com/apache/pulsar/discussions/17988#discussioncomment-3862645 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 Client C++ Release 3.0.0 Candidate 1
On Wed, Oct 12, 2022 at 9:02 AM Matteo Merli wrote: > Honestly, I don't know why it was ever documented in the README. BTW: it turns out it was me who added these scripts in the README, in 2017 臘 -- Matteo Merli
[GitHub] [pulsar] goncalocribeiro edited a comment on the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency
GitHub user goncalocribeiro edited a comment on the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency Hi Michael, Actually I found out that I only need the pulsar-broker-common dependency, and by excluding the pulsar-zookeeper-utils dependency it works: org.apache.pulsar pulsar-broker-common 2.9.3 org.apache.pulsar pulsar-zookeeper-utils I've tried before, to execute mvn dependency:tree, but the process just get stuck... so I couldn't get through that. GitHub link: https://github.com/apache/pulsar/discussions/17988#discussioncomment-3861924 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 Client C++ Release 3.0.0 Candidate 1
-- Matteo Merli On Tue, Oct 11, 2022 at 7:35 PM Michael Marshall wrote: > > I am getting an error when building from the downloaded source tarball > while following the instructions in the README. I get this error: > > $ ./docker-build.sh > fatal: not a git repository (or any of the parent directories): .git docker-build.sh was a script created for CI in the old repo. It doesn't make sense for someone to compile inside Docker because the resulting library will most likely not be usable in their environment. Honestly, I don't know why it was ever documented in the README. Since we're not using it anymore in CI, we should remove it. I created a PR https://github.com/apache/pulsar-client-cpp/pull/46 > I am not certain, but it seems like we need to end this vote and fix > the build script so that users can build from source. Let me know what > you think. I would suspect that not many people would be trying to compile with the docker script and the other instructions to build from source should all be working already. In any case, we can remove them and create a new candidate.
[GitHub] [pulsar] goncalocribeiro added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency
GitHub user goncalocribeiro added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency Hi Michael, Actually I found out that I only need the pulsar-broker-common dependency, and by excluding the pulsar-zookeeper-utils dependency it works: org.apache.pulsar pulsar-broker-common 2.9.3 org.apache.pulsar pulsar-zookeeper-utils I've tried before, to execute mvn dependency:tree, but the process just get stuck... so I couldn't get throw that. GitHub link: https://github.com/apache/pulsar/discussions/17988#discussioncomment-3861924 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] michaeljmarshall added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency
GitHub user michaeljmarshall added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency The break in binary compatibility was introduced here https://github.com/apache/pulsar/pull/15329, and fixed here, https://github.com/apache/pulsar/pull/16794. It should be fixed the 2.9.4 release, but that is not available yet. In order to use 2.9.3, you'll need to recompile the project, like you're trying to do. As for being unable to download the dependency, that sounds like a separate issue. Do you have any logs? When you build the dependency tree, do you see a circular dependency? After quickly searching, I don't see any related issues. GitHub link: https://github.com/apache/pulsar/discussions/17988#discussioncomment-3861802 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] HenriqueFSilva added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency
GitHub user HenriqueFSilva added a comment to the discussion: Importing pulsar-broker:2.9.3 or 2.10.1 maven dependency I have the same issue, would really like some feedback on this :) GitHub link: https://github.com/apache/pulsar/discussions/17988#discussioncomment-3860703 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] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
+1 On Wed, Oct 12, 2022, 7:49 AM Xiangying Meng wrote: > +1 > > Thanks, > Xiangying > > On Wed, Oct 12, 2022 at 7:11 PM Haiting Jiang > wrote: > > > +1 > > > > Thanks, > > Haiting > > > > On Wed, Oct 12, 2022 at 5:46 PM houxiaoyu wrote: > > > > > > +1 > > > Very useful. > > > > > > Michael Marshall 于2022年10月12日周三 12:52写道： > > > > > > > Hi All, > > > > > > > > I had a brief discussion with Matteo about mailing list notifications > > > > for our apache/pulsar-* repos in this PR > > > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it > for > > > > additional context. > > > > > > > > The outcome is a proposal to make all of our GitHub repos send their > > > > notifications to commits@ instead of dev@. Contributors will be able > > > > to subscribe to updates by using the GitHub "watch" feature. > > > > > > > > I created a sample PR here: > > > > https://github.com/apache/pulsar-client-go/pull/861. > > > > > > > > If there are no major objections, I plan to move forward with the > rest > > > > of our repos later this week. > > > > > > > > Thanks, > > > > Michael > > > > > > >
Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
+1 Thanks, Xiangying On Wed, Oct 12, 2022 at 7:11 PM Haiting Jiang wrote: > +1 > > Thanks, > Haiting > > On Wed, Oct 12, 2022 at 5:46 PM houxiaoyu wrote: > > > > +1 > > Very useful. > > > > Michael Marshall 于2022年10月12日周三 12:52写道： > > > > > Hi All, > > > > > > I had a brief discussion with Matteo about mailing list notifications > > > for our apache/pulsar-* repos in this PR > > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it for > > > additional context. > > > > > > The outcome is a proposal to make all of our GitHub repos send their > > > notifications to commits@ instead of dev@. Contributors will be able > > > to subscribe to updates by using the GitHub "watch" feature. > > > > > > I created a sample PR here: > > > https://github.com/apache/pulsar-client-go/pull/861. > > > > > > If there are no major objections, I plan to move forward with the rest > > > of our repos later this week. > > > > > > Thanks, > > > Michael > > > >
Re: [VOTE] Pulsar Client C++ Release 3.0.0 Candidate 1
Hi, Michael, The failure is caused by the wrong format, here is the fix: https://github.com/apache/pulsar-client-cpp/pull/45 We should include this PR and begin another vote process. However, IMO, these `docker-*.sh` should be removed in future. `docker-build.sh` was original written for tests within a image that contains all required dependencies. The libraries built by `docker-build.sh` should not be delivered because the dependencies are all dynamically linked. Maintaining a based image manually is not good. As we can see from the existing workflow [1], installing dependencies quickly for test is not complicated. And there are also some build related scripts but unfortunately not documented yet. For RedHat and Debian users, they can install the rpm [2] or deb [3] binaries in https://dist.apache.org/repos/dist/dev/pulsar/pulsar-client-cpp-3.0.0-candidate-1/. These binaries are statically linked. For those want to compile from source, they can follow the guide here: https://github.com/apache/pulsar-client-cpp#compilation [1] https://github.com/apache/pulsar-client-cpp/blob/aa8347724c217b8c2ff8513fbcaae00df5c97dc9/.github/workflows/ci-pr-validation.yaml#L43-L56 [2] https://pulsar.apache.org/docs/client-libraries-cpp#install-rpm [3] https://pulsar.apache.org/docs/client-libraries-cpp#install-debian Thanks, Yunze > On Oct 12, 2022, at 10:35, Michael Marshall wrote: > > I am getting an error when building from the downloaded source tarball > while following the instructions in the README. I get this error: > > $ ./docker-build.sh > fatal: not a git repository (or any of the parent directories): .git > > The issue is in the script. I believe we have already solved this in > the apache/pulsar repo. > > I am not certain, but it seems like we need to end this vote and fix > the build script so that users can build from source. Let me know what > you think. > > Before getting to the above issues, I verified the following: > > - Verified signatures for 33 artifacts. All are signed using > C46D6658489DDE09CE938AF87B6A6401BF99B4A3. > - Verified checksums for 33 artifacts. > > - Verified source equivalence between the original apache/pulsar repo > and the apache/pulsar-client-cpp repo by using diff and comparing > relevant commit hashes. I checked out > 4a864f20530e230ecee7e4ab09430bd65fb9789c for pulsar-client-cpp and > 5f079433c3706d994e6d0210cfc87e483ad53e52 for pulsar. Below is the > resulting diff. > > $ diff pulsar-client-cpp/ pulsar/pulsar-client-cpp/ > Only in pulsar-client-cpp/: .git > Common subdirectories: pulsar-client-cpp/build-support and > pulsar/pulsar-client-cpp/build-support > Common subdirectories: pulsar-client-cpp/cmake_modules and > pulsar/pulsar-client-cpp/cmake_modules > Common subdirectories: pulsar-client-cpp/docker and > pulsar/pulsar-client-cpp/docker > Common subdirectories: pulsar-client-cpp/docs and > pulsar/pulsar-client-cpp/docs > Common subdirectories: pulsar-client-cpp/examples and > pulsar/pulsar-client-cpp/examples > Common subdirectories: pulsar-client-cpp/include and > pulsar/pulsar-client-cpp/include > Common subdirectories: pulsar-client-cpp/lib and pulsar/pulsar-client-cpp/lib > Common subdirectories: pulsar-client-cpp/perf and > pulsar/pulsar-client-cpp/perf > Common subdirectories: pulsar-client-cpp/pkg and pulsar/pulsar-client-cpp/pkg > Common subdirectories: pulsar-client-cpp/python and > pulsar/pulsar-client-cpp/python > Common subdirectories: pulsar-client-cpp/templates and > pulsar/pulsar-client-cpp/templates > Common subdirectories: pulsar-client-cpp/test-conf and > pulsar/pulsar-client-cpp/test-conf > Common subdirectories: pulsar-client-cpp/tests and > pulsar/pulsar-client-cpp/tests > Common subdirectories: pulsar-client-cpp/wireshark and > pulsar/pulsar-client-cpp/wireshark > > Also, if we look at tag v3.0.0-candidate-1, the diff shows that the > primary changes being voted on are changes to the build: > > $ diff pulsar-client-cpp/ pulsar/pulsar-client-cpp/ -q > Only in pulsar-client-cpp/: .asf.yaml > Only in pulsar-client-cpp/: .git > Only in pulsar-client-cpp/: .github > Files pulsar-client-cpp/.gitignore and > pulsar/pulsar-client-cpp/.gitignore differ > Files pulsar-client-cpp/CMakeLists.txt and > pulsar/pulsar-client-cpp/CMakeLists.txt differ > Only in pulsar-client-cpp/: CONTRIBUTING.md > Only in pulsar-client-cpp/: LICENSE > Only in pulsar-client-cpp/: NOTICE > Files pulsar-client-cpp/README.md and pulsar/pulsar-client-cpp/README.md > differ > Only in pulsar-client-cpp/: SECURITY.md > Common subdirectories: pulsar-client-cpp/build-support and > pulsar/pulsar-client-cpp/build-support > Common subdirectories: pulsar-client-cpp/cmake_modules and > pulsar/pulsar-client-cpp/cmake_modules > Only in pulsar-client-cpp/: dependencies.yaml > Common subdirectories: pulsar-client-cpp/docker and > pulsar/pulsar-client-cpp/docker > Only in pulsar/pulsar-client-cpp/: docker-build-centos7.sh > Only in pulsar/pulsar-client-cpp/:
Re: [VOTE] Pulsar Release 2.10.2 Candidate 2
Hi all, > The fixed PR is here: > https://github.com/apache/pulsar/pull/17948 This PR is merged and cherry-picked to branch-2.10. I am about to start RC3 for 2.10.2 , If you have any other release blockers, please let me know. Thanks, Haiting On Sat, Oct 8, 2022 at 3:46 PM Haiting Jiang wrote: > > Hi Xiaoyu, > > > The fixed PR is here: > > https://github.com/apache/pulsar/pull/17948 > > > > This should be a release blocker I think. > > Great catch, Thank you! > The publish throughput is down by almost half with default setup, this > is definitely a release blocker. > > Thanks, > Haiting > > On Sat, Oct 8, 2022 at 12:58 PM houxiaoyu wrote: > > > > Hi Haiting, > > > > There is a significant performance regression about publish > > throughput, more context is here: > > https://github.com/apache/pulsar/issues/17931 > > > > The fixed PR is here: > > https://github.com/apache/pulsar/pull/17948 > > > > This should be a release blocker I think. > > > > Thanks, > > Xiaoyu Hou > > > > Haiting Jiang 于2022年10月6日周四 10:46写道： > > > > > This is the second release candidate for Apache Pulsar, version 2.10.2. > > > > > > This release contains 249 commits by 57 contributors. > > > https://github.com/apache/pulsar/compare/v2.10.1...v2.10.2-candidate-2 > > > > > > CI for this release candidate > > > https://github.com/Jason918/pulsar/pull/10 > > > > > > *** 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-2/ > > > > > > SHA-512 checksums: > > > > > > 26dc11e1514aa286d934e2f9698f4a04def6424307dcc452324bf935e88ba97c2d75b480a88a98640010c0117293d128e389c3e4fa98ab51cfc19e9312f5d00a > > > ./apache-pulsar-2.10.2-bin.tar.gz > > > > > > 0eee2f47680966736acbdbdf309b0c7ccd4d10f737f49b6b8d9f5599a51d46568c1a0a18c75be6a44f78da60fe4287889d2e158fe530b20cee8b64411abe65f0 > > > ./apache-pulsar-2.10.2-src.tar.gz > > > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachepulsar-1186/ > > > > > > The tag to be voted upon: > > > v2.10.2-candidate-2 (850c9448a5ac32e2f94988b8bf80955c93ef9d6c) > > > https://github.com/apache/pulsar/releases/tag/v2.10.2-candidate-2 > > > > > > 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-1ef93f17102e8193fc625fd5572f431d45935f7e2f11add3725a301c4321cef4 > > > > > > https://hub.docker.com/layers/jason918/pulsar-all/2.10.2/images/sha256-6e6b49687b7debdf26feb71fedaa622de425885de5e2e7498dc476867cab85bc > > > > > > 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: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
+1 Thanks, Haiting On Wed, Oct 12, 2022 at 5:46 PM houxiaoyu wrote: > > +1 > Very useful. > > Michael Marshall 于2022年10月12日周三 12:52写道： > > > Hi All, > > > > I had a brief discussion with Matteo about mailing list notifications > > for our apache/pulsar-* repos in this PR > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it for > > additional context. > > > > The outcome is a proposal to make all of our GitHub repos send their > > notifications to commits@ instead of dev@. Contributors will be able > > to subscribe to updates by using the GitHub "watch" feature. > > > > I created a sample PR here: > > https://github.com/apache/pulsar-client-go/pull/861. > > > > If there are no major objections, I plan to move forward with the rest > > of our repos later this week. > > > > Thanks, > > Michael > >
Re: [DISCUSS] Planning for Apache Pulsar 3.0
Il giorno mer 12 ott 2022 alle ore 00:40 Matteo Merli ha scritto: > > Agree, though let's make separate discussions. Putting all random > ideas into the same cauldron is a good recipe for making no one able > to follow or see a common line. > > That's what I meant when I started the proposal of having 3.0 > completely detached from "features". > > If you start making a big container, you're going to fill it up with > all the "breaking changes" that you want to include, because "hey, > that's the only window of opportunity". That in turn is the surest way > to not ship anything for the next 24 months, as all the changes are > unavoidably going to get delayed and will take a long time to > stabilize. > > Going back to API breakages: > 1. We never break wire protocol compatibility > 2. We try to never break client API > 3. We need a very good & compelling reason in order to break client API > 4. When we do so, we need to provide a clear path for users (eg: > pulsar-client-1.x compatibly drop-in). I totally agree with Matteo and Joe, We cannot break compatibility. and if we need to introduce some new form of inter-broker communication protocol we must support the current protocol and provide a smooth upgrade path. Now there are many Pulsar clusters around the world that cannot tolerate stop-the-world upgrades and we MUST also allow some sort of rollback in case of problems. Enrico > > > > > > > -- > Matteo Merli > > > On Tue, Oct 11, 2022 at 11:58 AM Dave Fisher wrote: > > > > Let’s discuss any and all ideas for improvement. As each is discussed we > > can figure out how to make them non-breaking, We all want Pulsar to improve. > > > > We should encourage an open discussion where no idea is automatically bad > > or wrong. They can just be discussed without fear. > > > > Thanks, > > Dave > > > > > On Oct 10, 2022, at 3:05 PM, Joe F wrote: > > > > > > I would prefer that we avoid using the term “breaking changes”, which is > > > too vague to convey any specific meaning. So let me try to bring some > > > clarity. > > > > > > > > > There have been many changes to implementations, APIs and data storage > > > formats in Pulsar (and book keeper also). I have deployed many of these > > > changes to production. And I know that Matteo and Rajan (and others too, > > > about whom I’m not up to date on) have implemented and deployed many > > > such > > > changes. But none of those changes ever required taking the system > > > offline. NONE. > > > > > > > > > Pulsar was developed as a 24x7x365 system, and rolling upgrades and > > > rollbacks were a given. Like “this is water”, there was no special > > > callout > > > needed for declaring this reality. No change, including enhancements to > > > wire protocols, broke client compatibility. Existing clients continued to > > > work; they may not be able to use all the new features. Use of new > > > features > > > would require the app to be rebuilt anyway. (Checksums, e2e encryption > > > are > > > examples) > > > > > > > > > We have even succeeded in getting Pulsar adopted for some use cases, just > > > because the complexity of upgrading from K’s old clients to new ones were > > > costly enough to allow consideration of an alternative like Pulsar. The > > > business cost of forcing a client upgrade can be significant, to the > > > point > > > of this being unviable for business. That just cannot be hand-waved over > > > > > > > > > There have also been changes in storage formats(the ZK metadata change > > > from > > > text to binary is an example). But through all such changes, compatibility > > > and upgradeability has been a given. There has never been a situation > > > where > > > a live Pulsar upgrade was not possible, and a coordinated client > > > upgrade > > > was mandatory. > > > > > > > > > So the question should not be about whether “signifcant” changes should > > > be made or not. Changes can be made and released in a way that breaks > > > *business*, or they can be made in a way that lets businesses sail > > > smoothly through that change. So the question is about how such changes > > > gets rolled out. > > > > > > > > > And to that question, my strong opinion is that any change that does not > > > allow a live/rolling upgrade or rollback, or anything that forces a client > > > to upgrade just to continue functioning, is a non-starter. All changes > > > can be made in a compatible, phased manner, and in a way that does not > > > penalise older versions ( older versions doing worse on new releases is > > > also not an acceptable way of making changes) Changes can be made in a > > > manner that make l A/B testing possible by the user, with limited risk, > > > and > > > then choosing to a not go back. It has all been done in Pulsar before. > > > > > > > > > Would that be harder than just breaking stuff? Yes. But that is far more > > > preferable than forcing users to take a hit. > > > > > > > > > -joe > > > >
[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #114: When i run test console app consumer is creating and when i integrate same to actual product consumer is not creating and going to F
blankensteiner commented on issue #114: URL: https://github.com/apache/pulsar-dotpulsar/issues/114#issuecomment-1275909511 Yes, the console app should also fail in that case. Did you try with a producer? Also, are you running on Windows or Linux, and what dependencies does your production app have? -- 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
Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
+1 Very useful. Michael Marshall 于2022年10月12日周三 12:52写道： > Hi All, > > I had a brief discussion with Matteo about mailing list notifications > for our apache/pulsar-* repos in this PR > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it for > additional context. > > The outcome is a proposal to make all of our GitHub repos send their > notifications to commits@ instead of dev@. Contributors will be able > to subscribe to updates by using the GitHub "watch" feature. > > I created a sample PR here: > https://github.com/apache/pulsar-client-go/pull/861. > > If there are no major objections, I plan to move forward with the rest > of our repos later this week. > > Thanks, > Michael >
Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
+1 Enrico Il giorno mer 12 ott 2022 alle ore 09:11 Nicolò Boschi ha scritto: > > Absolutely +1 > Thanks Michael > > > Nicolò Boschi > > > Il giorno mer 12 ott 2022 alle ore 08:56 Yu ha scritto: > > > +1, thank you, Michael! > > > > > > On Wed, Oct 12, 2022 at 1:00 PM Matteo Merli > > wrote: > > > > > +1 Thanks Michael for fixing these! > > > > > > > > > > > > On Tue, Oct 11, 2022 at 9:52 PM Michael Marshall > > > wrote: > > > > > > > Hi All, > > > > > > > > I had a brief discussion with Matteo about mailing list notifications > > > > for our apache/pulsar-* repos in this PR > > > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it for > > > > additional context. > > > > > > > > The outcome is a proposal to make all of our GitHub repos send their > > > > notifications to commits@ instead of dev@. Contributors will be able > > > > to subscribe to updates by using the GitHub "watch" feature. > > > > > > > > I created a sample PR here: > > > > https://github.com/apache/pulsar-client-go/pull/861. > > > > > > > > If there are no major objections, I plan to move forward with the rest > > > > of our repos later this week. > > > > > > > > Thanks, > > > > Michael > > > > > > > -- > > > -- > > > Matteo Merli > > > > > > > >
[GitHub] [pulsar] BewareMyPower added a comment to the discussion: Python 3.6 client for aarch64/arm64 Linux?
GitHub user BewareMyPower added a comment to the discussion: Python 3.6 client for aarch64/arm64 Linux? https://github.com/apache/pulsar/pull/17733 The first ARM based official image might be released by 2.12.0 or later. GitHub link: https://github.com/apache/pulsar/discussions/17994#discussioncomment-3858409 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] swjz added a comment to the discussion: Python 3.6 client for aarch64/arm64 Linux?
GitHub user swjz added a comment to the discussion: Python 3.6 client for aarch64/arm64 Linux? Thanks a lot! One more thing, is there a docker image for ARM arch as well? I see on https://hub.docker.com/r/apachepulsar/pulsar/tags there seems to be `linux/amd64` images only, and if I pull up that image, I'm getting this error: ``` $ sudo docker run -it --name pulsar -p 6650:6650 -p 8080:8080 --mount source=pulsardata,target=/pulsar/data --mount source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:2.10.1 bin/pulsar standalone WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested standard_init_linux.go:228: exec user process caused: exec format error ``` GitHub link: https://github.com/apache/pulsar/discussions/17994#discussioncomment-3858364 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-client-node] RobertIndie opened a new pull request, #234: feat: Add chunking support
RobertIndie opened a new pull request, #234: URL: https://github.com/apache/pulsar-client-node/pull/234 ### Motivation This is the nodejs client feature catch up for [PIP 37](https://github.com/apache/pulsar/wiki/PIP-37%3A-Large-message-size-handling-in-Pulsar) ### Modifications * Add `chunkingEnabled ` to the producer configuration * Add `maxPendingChunkedMessage` and `autoAckOldestChunkedMessageOnQueueFull ` to the consumer configuration -- 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
Pulsar Release Note Website and Guide
Hi community and release managers, For the Pulsar Release Note website [1], here is some good news: # 1 We've simplified the workflow of submitting Pulsar release notes. I've documented the workflow and everything about the Pulsar Release Note website in the *Pulsar Release Note Guide* [2]. Please follow the steps there. # 2 Now, the Pulsar Release Note website is generated automatically. This great work is done by @signormercurio and @urfreespace! [4] Huge THANKS to you! Feel free to comment if you have any questions or suggestions. Yu [1] https://pulsar.apache.org/release-notes/ [2] https://github.com/apache/pulsar/blob/master/wiki/release/release-note-guide.md Note: the workflow of submitting release notes for C++ and Python clients might be changed in recent days. Context see https://github.com/apache/pulsar/issues/17918#issuecomment-1273075920 [3] https://github.com/apache/pulsar/discussions/17310
Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
Absolutely +1 Thanks Michael Nicolò Boschi Il giorno mer 12 ott 2022 alle ore 08:56 Yu ha scritto: > +1, thank you, Michael! > > > On Wed, Oct 12, 2022 at 1:00 PM Matteo Merli > wrote: > > > +1 Thanks Michael for fixing these! > > > > > > > > On Tue, Oct 11, 2022 at 9:52 PM Michael Marshall > > wrote: > > > > > Hi All, > > > > > > I had a brief discussion with Matteo about mailing list notifications > > > for our apache/pulsar-* repos in this PR > > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it for > > > additional context. > > > > > > The outcome is a proposal to make all of our GitHub repos send their > > > notifications to commits@ instead of dev@. Contributors will be able > > > to subscribe to updates by using the GitHub "watch" feature. > > > > > > I created a sample PR here: > > > https://github.com/apache/pulsar-client-go/pull/861. > > > > > > If there are no major objections, I plan to move forward with the rest > > > of our repos later this week. > > > > > > Thanks, > > > Michael > > > > > -- > > -- > > Matteo Merli > > > > >
Re: [DISCUSS] Decrease GitHub email notifications from apache/pulsar-* repos to this ML
+1, thank you, Michael! On Wed, Oct 12, 2022 at 1:00 PM Matteo Merli wrote: > +1 Thanks Michael for fixing these! > > > > On Tue, Oct 11, 2022 at 9:52 PM Michael Marshall > wrote: > > > Hi All, > > > > I had a brief discussion with Matteo about mailing list notifications > > for our apache/pulsar-* repos in this PR > > https://github.com/apache/pulsar-client-cpp/pull/42. Please see it for > > additional context. > > > > The outcome is a proposal to make all of our GitHub repos send their > > notifications to commits@ instead of dev@. Contributors will be able > > to subscribe to updates by using the GitHub "watch" feature. > > > > I created a sample PR here: > > https://github.com/apache/pulsar-client-go/pull/861. > > > > If there are no major objections, I plan to move forward with the rest > > of our repos later this week. > > > > Thanks, > > Michael > > > -- > -- > Matteo Merli > >
