[GitHub] [pulsar-site] urfreespace merged pull request #105: fix: auto replace some link that cause 404 before building

urfreespace merged PR #105: URL: https://github.com/apache/pulsar-site/pull/105 -- 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:

[GitHub] [pulsar-test-infra] Anonymitaet commented on a diff in pull request #43: Implement a new documentation bot

Anonymitaet commented on code in PR #43: URL: https://github.com/apache/pulsar-test-infra/pull/43#discussion_r894080305 ## docbot/action.yml: ## @@ -0,0 +1,12 @@ +name: 'Documentation Bot' +description: 'Automatically label pull requests based on the checked task list' +author:

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

If it will break historical behavior. I agree it should start with a discussion on the mailing list. And starting with a proposal is better. For this PR https://github.com/apache/pulsar/pull/15956 It will not break the existing behavior “The tenant admin can get schemas of a topic”. The tenant

Pulsar Community Meeting Notes 2022/06/09, (8:30 AM PST)

Hi Pulsar Community, Here are the meeting notes from today's community meeting. Thanks to all who participated! We had 3 detailed conversations, as the length of this email demonstrates. Disclaimer: If something is misattributed or misrepresented, please send a correction to this list. Source

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

I think we're running into an important edge case in our default authorization framework. Should the binary protocol and the REST API have the same levels of permission for a given role? For example, when I enable auto topic creation and give a role permission to produce to a namespace, that role

[GitHub] [pulsar-dotpulsar] wj8400684 opened a new issue, #106: Why does "pulse changed state to'faulted" appear when I connect to the server version 2.10.0

wj8400684 opened a new issue, #106: URL: https://github.com/apache/pulsar-dotpulsar/issues/106 Why does "pulse changed state to'faulted" appear when I connect to the server version 2.10.0 No problem with pulas2.7.1 -- This is an automated message from the Apache Git Service. To

Re: [DISCUSS] PIP-173 : Create a built-in Function implementing the most common basic transformations

Hi Neng, See the comment from Enrico in the PIP issue . We've put this in "Rejected alternatives" for the reasons that: - it won't be easily available to all Pulsar users - it would be hard to guarantee compatibility with many Pulsar versions,

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

I think it's an addition to the previously missing feature. It makes sense to me. Best, Mattison On Thu, 9 Jun 2022 at 22:24, PengHui Li wrote: > Hi Dave, > > This is a BUG fix. > > The binary protocol allows the produce/consume permission to get the > schema. > But the REST API is not

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

Hi Dave, This is a BUG fix. The binary protocol allows the produce/consume permission to get the schema. But the REST API is not allowed. The schema REST API was added very earlier and we found we have granted the consume permission to the user, but the user is not able to check what the

Re: [pulsar] branch master updated: [modify][admin] Change the permissions of the schema API from Admin to normal produce/consume (#15956)

Changes to admin permissions are decisions that require some discussion on dev@pulsar. Regards, Dave > On Jun 9, 2022, at 5:11 AM, techno...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > technoboy pushed a commit to branch master > in repository

[GitHub] [pulsar-test-infra] maxsxu opened a new pull request, #43: Implement a new documentation bot

maxsxu opened a new pull request, #43: URL: https://github.com/apache/pulsar-test-infra/pull/43 Master issue: https://github.com/apache/pulsar/issues/15797 ## Motivation As discussed at https://lists.apache.org/thread/tz7x73lnkvcg3vqmb9r26s4p6md5sb8y ## Modification

[GitHub] [pulsar-client-node] ibtesamlatif2997 opened a new issue, #218: Issue with node pre gyp

ibtesamlatif2997 opened a new issue, #218: URL: https://github.com/apache/pulsar-client-node/issues/218 On installation of node module. I am getting this error `node-pre-gyp WARN Tried to download(404):

[GitHub] [pulsar-client-node] ibtesamlatif2997 commented on issue #97: node-pre-gyp setup

ibtesamlatif2997 commented on issue #97: URL: https://github.com/apache/pulsar-client-node/issues/97#issuecomment-1150809103 Any update on this issue. I am facing the similar issue in docker -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [DISCUSS] Implementation for HTTP endpoint producer/consumer

> > If this is a REST endpoint then call it REST. It is very likely that users > will want to use HTTPS to use it. Calling it HTTP is a misnomer. Very thanks for your correction. Best, Mattison On Thu, 9 Jun 2022 at 15:37, mattison chao wrote: > I think building a separate HTTP server to

Re: [DISCUSS] Implementation for HTTP endpoint producer/consumer

> > I think building a separate HTTP server to serve REST produce/consume > requests might be a good idea, like FunctionWorkerService, users can choose > to run with broker for simplicity or run as a separate component if user > wants isolation and scale independently. Yes, it's a great

Re: [DISCUSS] PIP-174: Provide new implementation for broker dispatch cache

+1 Thanks, Aloys Hang Chen 于2022年6月8日周三 08:53写道： > +1 Great idea! > > Thanks, > Hang > > Lari Hotari 于2022年6月8日周三 03:32写道： > > > > This is a very useful proposal. LGTM > > > > -Lari > > > > On Tue, Jun 7, 2022 at 3:48 AM Matteo Merli > wrote: > > > > >