Re: New Pulsar website goes live!

Hi Sijie, Thanks for your timely response. We're looking into multi-language support and other known issues. Will keep the community updated once we make progress. On Fri, Feb 18, 2022 at 1:07 AM Sijie Guo wrote: > Maybe we should roll back to the old website first. > > - Sijie > > On Thu, Feb

Re: [Discuss][PIP-143] Support split paritions belonging to specified topics in a bundle

Hi Penghui, > I am considering if we can add a boundary param for split bundle API, > The boundary must be between the start and the end of the bundle. > looks like the followings: > > ```java > void splitNamespaceBundle(String namespace, String bundle, boolean > unloadSplitBundles, >

Re: [Discuss] Apache pulsar node client 1.6.0 release

+1 Hi Guangning, Thanks for starting the release! Here is the release process: https://github.com/apache/pulsar-client-node/wiki/Release-process If there is any question, feel free to let me know. In order to allow you to publish the artifact, I will invite you as a maintainer of the registry. C

Re: [Discuss] Apache pulsar node client 1.6.0 release

+1 BR//Huanli > On Feb 18, 2022, at 3:22 AM, Sijie Guo wrote: > > +1 > > On Thu, Feb 17, 2022 at 3:49 AM Guangning E wrote: > >> Recently many users want to use the oauth2 feature based on the node js >> client. I've added this feature, so I'd like to start a release for the >> pulsar node j

Re: [Discuss][PIP-143] Support split paritions belonging to specified topics in a bundle

Hi Aloys, Thanks for the great proposal. I am considering if we can add a boundary param for split bundle API, The boundary must be between the start and the end of the bundle. looks like the followings: ```java void splitNamespaceBundle(String namespace, String bundle, boolean unloadSplitBundle

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

+1 (binding) - Check signatures/checksums - Check the license headers - build sources - Validate Pub/Sub and Java Functions - Validate Stateful Functions Regards, Hiroyuki From: Michael Marshall Sent: Wednesday, February 16, 2022 13:34 To: Dev Subject: [VOT

Re: Rollback Pulsar Website Change

The website has been rolled back to the old one. - Sijie On Thu, Feb 17, 2022 at 12:37 PM Lari Hotari wrote: > Change to roll back Apache Pulsar Helm chart publishing to new site: > https://github.com/apache/pulsar-helm-chart/pull/234 > > -Lari > > On 2022/02/17 19:44:53 Sijie Guo wrote: > > ht

[GitHub] [pulsar-helm-chart] sijie merged pull request #234: [Build] Revert chart index publishing to new website (go back to publishing to apache/pulsar branch asf-site)

sijie merged pull request #234: URL: https://github.com/apache/pulsar-helm-chart/pull/234 -- 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-unsu

Re: Rollback Pulsar Website Change

Change to roll back Apache Pulsar Helm chart publishing to new site: https://github.com/apache/pulsar-helm-chart/pull/234 -Lari On 2022/02/17 19:44:53 Sijie Guo wrote: > https://github.com/apache/pulsar-site/pull/3 > https://github.com/apache/pulsar/pull/14356 > > Changes to roll back the websit

[GitHub] [pulsar-helm-chart] lhotari opened a new pull request #234: [Build] Revert chart index publishing to new website

lhotari opened a new pull request #234: URL: https://github.com/apache/pulsar-helm-chart/pull/234 - publish to the old website location, apache/pulsar , branch asf-site -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[GitHub] [pulsar-site] dave2wave commented on pull request #3: Revert "[PIP-87] Update .asf.yaml to publish the pulsar website from this branch"

dave2wave commented on pull request #3: URL: https://github.com/apache/pulsar-site/pull/3#issuecomment-1043401056 Perfect -- 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. T

[GitHub] [pulsar-site] merlimat merged pull request #3: Revert "[PIP-87] Update .asf.yaml to publish the pulsar website from this branch"

merlimat merged pull request #3: URL: https://github.com/apache/pulsar-site/pull/3 -- 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...

Re: Rollback Pulsar Website Change

https://github.com/apache/pulsar-site/pull/3 https://github.com/apache/pulsar/pull/14356 Changes to roll back the website. - Sijie On Thu, Feb 17, 2022 at 11:30 AM Sijie Guo wrote: > Hi all, > > All the Pulsar links out there (Google, Stackoverflow, etc) are broken. I > am sending PRs to rollb

[GitHub] [pulsar-site] sijie opened a new pull request #3: Revert "[PIP-87] Update .asf.yaml to publish the pulsar website from this branch"

sijie opened a new pull request #3: URL: https://github.com/apache/pulsar-site/pull/3 This reverts commit fbeb3f81a11b5b469c430877f8698ee7e3ea21fe. -- 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 t

Rollback Pulsar Website Change

Hi all, All the Pulsar links out there (Google, Stackoverflow, etc) are broken. I am sending PRs to rollback the website push. - Sijie

Re: [Discuss] Apache pulsar node client 1.6.0 release

+1 On Thu, Feb 17, 2022 at 3:49 AM Guangning E wrote: > Recently many users want to use the oauth2 feature based on the node js > client. I've added this feature, so I'd like to start a release for the > pulsar node js 1.6.0 client. > > > > > Thanks, > Guangning >

Re: [Discuss] Apache pulsar node client 1.6.0 release

+1 ( no need to add user@ next time) Enrico Il Gio 17 Feb 2022, 16:05 PengHui Li ha scritto: > +1 > > Penghui > > On Thu, Feb 17, 2022 at 7:49 PM Guangning E wrote: > > > Recently many users want to use the oauth2 feature based on the node js > > client. I've added this feature, so I'd like

[GitHub] [pulsar-helm-chart] smazurov opened a new pull request #233: feat(certs): use actual v1 spec for certs

smazurov opened a new pull request #233: URL: https://github.com/apache/pulsar-helm-chart/pull/233 ### Motivation In #204, api version of the cert resources was updated to v1. This was insufficient because `v1` has different spec from `v1alpha1` This MR finishes the work that

Re: New Pulsar website goes live!

Maybe we should roll back to the old website first. - Sijie On Thu, Feb 17, 2022 at 8:33 AM Sijie Guo wrote: > Remove users@ > > Yu - I have received quite a few questions about broken links. > > https://pulsar.apache.org/docs/en/security-jwt/ <- This is broken. > > It seems to be me that it is

Re: New Pulsar website goes live!

Remove users@ Yu - I have received quite a few questions about broken links. https://pulsar.apache.org/docs/en/security-jwt/ <- This is broken. It seems to be me that it is related to multi-language support. Is anyone looking into fixing it? - Sijie On Thu, Feb 17, 2022 at 1:50 AM Yu wrote:

Re: [DISCUSS] PIP-142 Increase default numHttpServerThreads value to 200 to prevent Admin API unavailability

On Thu, Feb 17, 2022 at 3:12 AM Yunze Xu wrote: > And we should make it clear whether numHttpServerThread=200 could > solve the existing problem like > https://github.com/apache/pulsar/pull/13666 > Changing the number of threads won't do anything to

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

+1 (non binding) Checks: - 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 - Deployed a cluster to a k8s env and tested simple functions (k8s mode) and the elastic sink usin

[Discuss][PIP-143] Support split paritions belonging to specified topics in a bundle

Hi Pulsar Community, This is a PIP discussion on how to support split partitions belonging to specified topics in a bundle. The issue can be found: https://github.com/apache/pulsar/issues/13761 I copy the content here for convenience, any suggestions are welcome and appreciated. ## Motivation

Re: [Discuss] Apache pulsar node client 1.6.0 release

+1 Penghui On Thu, Feb 17, 2022 at 7:49 PM Guangning E wrote: > Recently many users want to use the oauth2 feature based on the node js > client. I've added this feature, so I'd like to start a release for the > pulsar node js 1.6.0 client. > > > > > Thanks, > Guangning >

Re: [DISCUSS] Apache Pulsar 2.10.0 release

Thanks, Rui I have merged the PR and cherry-picked it into branch-2.10, I will take care of the tests of branch-2.10 and do more tests. Regards, Penghui On Thu, Feb 17, 2022 at 6:42 PM Rui Fu wrote: > Hi all, > > For https://github.com/apache/pulsar/pull/13376, I have done some tests > to veri

[GitHub] [pulsar-helm-chart] frankjkelly commented on pull request #190: Bump to Pulsar 2.8.2

frankjkelly commented on pull request #190: URL: https://github.com/apache/pulsar-helm-chart/pull/190#issuecomment-1042976170 @lhotari are any of these changes (esp. the JVM setting changes) backwards incompatible with `2.7.x` Pulsar? Just wondering if I can mix-and-match this `2.8.x` hel

[Discuss] Apache pulsar node client 1.6.0 release

Recently many users want to use the oauth2 feature based on the node js client. I've added this feature, so I'd like to start a release for the pulsar node js 1.6.0 client. Thanks, Guangning

Re: New Feature Proposal: flag to require a non-partitioned topic on Producer/Consumer Builder

Sijie, Il Gio 17 Feb 2022, 07:13 Michael Marshall ha scritto: > > Ideally, people shouldn't be aware of partitioned vs non-partitioned. > Sometimes it is a requirement to have a non-partioned topic and the application will misbehave if running on a partitioned topic with more than one partition

Re: [DISCUSS] PIP-142 Increase default numHttpServerThreads value to 200 to prevent Admin API unavailability

My only concern is the same with Matteo: > Dedicating 200 threads to that would be > a massive waste of resources (CPU & memory). And we should make it clear whether numHttpServerThread=200 could solve the existing problem like https://github.com/apache/pulsar/pull/13666

[GitHub] [pulsar-client-node] tuteng merged pull request #194: Fixed windows install client

tuteng merged pull request #194: URL: https://github.com/apache/pulsar-client-node/pull/194 -- 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-un

Re: [DISCUSS] Apache Pulsar 2.10.0 release

Hi all, For https://github.com/apache/pulsar/pull/13376, I have done some tests to verify the upgrade of Pulsar Functions from root image to non-root image. The test runs on my local machine with KinD cluster, with a fresh Pulsar +auth 2.8.2 cluster. The cluster uses Kubernetes Runtime and multi

[GitHub] [pulsar-site] urfreespace opened a new pull request #2: [WIP]fix: sync workflow

urfreespace opened a new pull request #2: URL: https://github.com/apache/pulsar-site/pull/2 Don't merge it until [https://github.com/apache/pulsar/pull/14344](14344) merged -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

Re: New Pulsar website goes live!

Thanks Sijie. Hi Pulsarers, Since we're switching the website, please DO NOT MERGE DOC RELATED PRS NOW until this change [1] gets merged. We're working in progress and will keep you updated ASAP. If you encounter any issues on the new Pulsar website, do not hesitate to add it here [2], thanks.

Re: [VOTE] Pulsar Release 2.8.3 Candidate 2

+1 - Check src build - Check run standalone mode by binary package - Check Basic publish and consume partitioned topic - Check Pulsar SQL query bytes data On 2022/02/16 04:34:55 Michael Marshall wrote: > This is the second release candidate for Apache Pulsar, version 2.8.3. > > It fixes the foll