[GitHub] [pulsar-site] urfreespace merged pull request #87: fix: sine wave undefine

[GitBox]

urfreespace merged PR #87:
URL: https://github.com/apache/pulsar-site/pull/87


-- 
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: PIP-156: Build and Run Pulsar Server on Java 17

[Heesung Sohn]

Hi,

As a follow-up task here, I have a proposal to update pulsar server default
GC configs. I tried to summarize the details in my fork PR:
https://github.com/heesung-sn/pulsar/pull/1, and It would be great if I
could get some early feedback from the community.

Thank you,
Heesung

On Thu, Apr 21, 2022 at 4:00 AM Jiuming Tao 
wrote:

> +1
> Thanks,
> Tao Jiuming
>
> > 2022年4月19日 上午2:25，Heesung Sohn 
> 写道：
> >
> > Dear Pulsar dev community,
> >
> > My name is Heesung Sohn, and I would like to open a discussion here
> > about PIP-156:
> > Build and Run Pulsar Server on Java 17
> > .
> >
> >
> > @Nicolò Boschi,
> > I see your similar PR  for
> the
> > Java 17 runtime support. Since some of the Java 17 upgrade work could
> > overlap, it would be great if we can discuss how to collaborate too --
> for
> > this PIP, we need to additionally update the `javac --release` option to
> > Java 17.
> >
> > Regards,
> > Heesung
> > --
> >
> > 
> >
> > Heesung Sohn
> >
> > Platform Engineer
> >
> > e: heesung.s...@streamnative.io
> >
> > streamnative.io
> >
> > 
> > 
> > 
>
>

[GitHub] [pulsar-site] dave2wave opened a new issue, #86: Only Index Docs from Currently Supported Versions

[GitBox]

dave2wave opened a new issue, #86:
URL: https://github.com/apache/pulsar-site/issues/86

   In Algolia there is a crawler configuration which skips "incubating" docs. I 
think that we should stop creating an index for versions of pulsar components 
which are no longer supporting.
   
   (1) We can either remove these pages from the site.
   
   or more likely
   
   (2) Include those versions in the exclude pattern.


-- 
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.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] dave2wave opened a new issue, #85: Sitemap URLs should have the trailing '/'

[GitBox]

dave2wave opened a new issue, #85:
URL: https://github.com/apache/pulsar-site/issues/85

   In the website many urls are left bare without the trailing '/'. The website 
redirects these to the url with the '/'. In working with the Algolia crawler it 
spends time scanning one and then the other.
   
   I think if the `sitemap.xml` was generated with the '/' then we might get 
better search results from a google search.
   
   For example:
   ```
   
   
   https://pulsar.apache.org/blog/2021/05/13/Apache-Pulsar-2-7-2/
   
   weekly
   0.5
   
   ```


-- 
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.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [pulsar-site] dave2wave merged pull request #84: Update Algolia API Key

[GitBox]

dave2wave merged PR #84:
URL: https://github.com/apache/pulsar-site/pull/84


-- 
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-site] dave2wave opened a new pull request, #84: Update Algolia API Key

[GitBox]

dave2wave opened a new pull request, #84:
URL: https://github.com/apache/pulsar-site/pull/84

   The key does not match. I'm checking for other issues before I merge this


-- 
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: [VOTE] Pulsar Manager Release 0.3.0 Candidate 3

[Max Xu]

+1 (non-binding)

- Validate checksum
- Start pulsar-manager
- Create an environment (add a pulsar instance)
- Create and delete tenants/namespaces/topics. But unable to create token

Thanks,
Max Xu



On Wed, May 18, 2022 at 6:58 PM Hang Chen  wrote:

> +1(binding)
> - Validate checksum
> - Deploy pulsar-manager service and add pulsar cluster
> - Create tenants, namespace and topics, delete topics.
>
> Thanks,
> Hang
>
> Guangning E  于2022年5月12日周四 20:39写道：
> >
> > +1(non-binding)
> > Validate checksum
> > Start pulsar-manager service
> > Create tenant and topic
> >
> > Thanks,
> > Guangning
> >
> > Li Li  于2022年5月10日周二 14:14写道：
> >
> > > Hi everyone,
> > > Please review and vote on the release candidate #3 for the version
> 0.3.0,
> > > as follows:
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > The complete staging area is available for your review, which includes:
> > > * Release notes [1]
> > > * The official Apache source and binary distributions to be deployed to
> > > dist.apache.org  [2]
> > > * Source code tag "v0.3.0-candidate-3" [4] with git sha
> > >
> 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4
> > > apache-pulsar-manager-0.3.0-src.tar.gz
> > >
> > > PulsarManager's KEYS file contains PGP keys we used to sign this
> release:
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> > > https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> > >
> > > Please download these packages and review this release candidate:
> > >
> > > - Review release notes
> > > - Download the source package (verify shasum, and asc) and follow the
> > > instructions to build and run the pulsar-manager front end and back end
> > > service.
> > > - Download the binary package (verify shasum, and asc) and follow the
> > > instructions to run run the pulsar-manager front end and back end
> service.
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > >
> > > Source and binary files:
> > >
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz
> > > <
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz
> > > >
> > >
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz
> > > <
> > >
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz
> > > >
> > >
> > > SHA-512 checksums:
> > >
> > >
> 6ffa5921765ee94a404792e98eb4b3cbda9e016c6661ef12e4e873e7e452301bc05650709955b012d08048e418133948a628ad55bc91ac65836022e1ea426d6f
> > > apache-pulsar-manager-0.3.0-bin.tar.gz
> > >
> 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4
> > > apache-pulsar-manager-0.3.0-src.tar.gz
> > >
> > >
> > >
> > >
>

[GitHub] [pulsar-site] SignorMercurio commented on issue #83: Wrong position settings for GitHub Stars badge

[GitBox]

SignorMercurio commented on issue #83:
URL: https://github.com/apache/pulsar-site/issues/83#issuecomment-1130088504

   /assign @SignorMercurio 


-- 
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-site] maxsxu commented on issue #83: Wrong position settings for GitHub Stars badge

[GitBox]

maxsxu commented on issue #83:
URL: https://github.com/apache/pulsar-site/issues/83#issuecomment-1130043063

   > I would like to help with this. Could you please assign this issue to me?
   
   @SignorMercurio  You should be able to use the `/assign` command


-- 
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-manager] dragonls closed issue #439: Support text filtering in Select component for tenant/namespace/topic

[GitBox]

dragonls closed issue #439: Support text filtering in Select component for 
tenant/namespace/topic
URL: https://github.com/apache/pulsar-manager/issues/439


-- 
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-manager] yws-tracy commented on issue #447: Deploy from bin package error

[GitBox]

yws-tracy commented on issue #447:
URL: https://github.com/apache/pulsar-manager/issues/447#issuecomment-1129904441

   is it resolved?  I met same issue


-- 
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-site] SignorMercurio commented on issue #83: Wrong position settings for GitHub Stars badge

[GitBox]

SignorMercurio commented on issue #83:
URL: https://github.com/apache/pulsar-site/issues/83#issuecomment-1129903904

   I would like to help with this. Could you please assign this issue to me?


-- 
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-site] SignorMercurio opened a new issue, #83: Wrong position settings for GitHub Stars badge

[GitBox]

SignorMercurio opened a new issue, #83:
URL: https://github.com/apache/pulsar-site/issues/83

   ## Current Behavior
   
   GitHub Stars badge overlaps with the light/dark mode toggle button on a 
normal 1425-px laptop screen:
   
   
![image](https://user-images.githubusercontent.com/32540679/169027834-d4c18ccd-7b13-43f4-8ebb-11ae6c80e311.png)
   
   When the browser window is resized to lower width, the badge will keep 
moving left:
   
   
![image](https://user-images.githubusercontent.com/32540679/169028046-00f3066a-b0dd-48af-b1fe-dda4f128c688.png)
   
   ## Expected Behavior
   
   The badge and the toggle button should never overlap, even when the browser 
window is resized.
   
   
![image](https://user-images.githubusercontent.com/32540679/169029399-eabb7f73-93fc-4c67-a4a1-4467fe6dd7d0.png)
   
   ## Possible Reason
   
   In [Line 193 in 
#77](https://github.com/apache/pulsar-site/pull/77/files#diff-09cf1119a5b3c2e7f9020e0631d965cc817f9ba589b4252cbb30ad92b403c4b6R193)
 a `right: 125px` style is introduced, leading to this issue.
   
   ## Possible Solution
   
   Use `padding` instead of horizontal absolute positioning styles like `right`.
   
   


-- 
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.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [VOTE] Pulsar Manager Release 0.3.0 Candidate 3

[Hang Chen]

+1(binding)
- Validate checksum
- Deploy pulsar-manager service and add pulsar cluster
- Create tenants, namespace and topics, delete topics.

Thanks,
Hang

Guangning E  于2022年5月12日周四 20:39写道：
>
> +1(non-binding)
> Validate checksum
> Start pulsar-manager service
> Create tenant and topic
>
> Thanks,
> Guangning
>
> Li Li  于2022年5月10日周二 14:14写道：
>
> > Hi everyone,
> > Please review and vote on the release candidate #3 for the version 0.3.0,
> > as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> > * Release notes [1]
> > * The official Apache source and binary distributions to be deployed to
> > dist.apache.org  [2]
> > * Source code tag "v0.3.0-candidate-3" [4] with git sha
> > 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4
> > apache-pulsar-manager-0.3.0-src.tar.gz
> >
> > PulsarManager's KEYS file contains PGP keys we used to sign this release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS <
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
> >
> > Please download these packages and review this release candidate:
> >
> > - Review release notes
> > - Download the source package (verify shasum, and asc) and follow the
> > instructions to build and run the pulsar-manager front end and back end
> > service.
> > - Download the binary package (verify shasum, and asc) and follow the
> > instructions to run run the pulsar-manager front end and back end service.
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> >
> > Source and binary files:
> >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz
> > <
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-bin.tar.gz
> > >
> >
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz
> > <
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-manager/apache-pulsar-manager-0.3.0/apache-pulsar-manager-0.3.0-src.tar.gz
> > >
> >
> > SHA-512 checksums:
> >
> > 6ffa5921765ee94a404792e98eb4b3cbda9e016c6661ef12e4e873e7e452301bc05650709955b012d08048e418133948a628ad55bc91ac65836022e1ea426d6f
> > apache-pulsar-manager-0.3.0-bin.tar.gz
> > 951095a71f7471dca028da0a330bc1a5e0707333a61fa4a09c8ea0f0a144d5628b511487e2442ebe290b9642b6b8ca7dee486a18a8339c893c37253724ad5fd4
> > apache-pulsar-manager-0.3.0-src.tar.gz
> >
> >
> >
> >

Breaking Changes in Pulsar Documentation

[Yu]

Hi everyone,
(especially documentation contributors)

As we've upgraded the Pulsar Website Framework (Docusarus), it brings some
breaking changes in writing and previewing documentation.

Please follow the rules below, or else you might encounter some errors.
- Pulsar Documentation Writing Syntax Guide [1]
- Pulsar Documentation Preview Guide [2]

Since we're redesigning the information architecture of the Pulsar website,
I'll optimize the contribution guide and add these guidelines there.

Feel free to comment if you have any suggestions or questions, thanks!

[1]
https://docs.google.com/document/d/12De2btkDHQVaqUlHjTqERmroMLKGhHdiC7rEttFTyqc/edit#heading=h.wu6ygjne8e35
[2]
https://docs.google.com/document/d/1wszdtMRo6MhKbVaggPK7_bnKaC4TewuT--GWZZxJNGg/edit#


Yu and Lili

[GitHub] [pulsar-manager] dockerzhang closed pull request #368: optimize default docker image for beginners

[GitBox]

dockerzhang closed pull request #368: optimize default docker image for 
beginners
URL: https://github.com/apache/pulsar-manager/pull/368


-- 
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: [VOTE] PIP-157: Bucketing topic metadata to allow more topics per namespace

[mattison chao]

+1 (non-binding)

Best,
Mattison

On Wed, 18 May 2022 at 15:20, Enrico Olivelli  wrote:

> +1 (binding)
>
> Enrico
>
> Il giorno mer 18 mag 2022 alle ore 08:54 Matteo Merli
>  ha scritto:
> >
> > +1
> >
> > --
> > Matteo Merli
> > 
> >
> > On Mon, May 2, 2022 at 6:40 PM Matteo Merli 
> wrote:
> > >
> > > Lari & Enrico, the discussion thread was out for 11 days and there
> > > were 2 positive feedbacks.
> > > I don't think this qualifies as "too early for a vote" and it would
> > > have been better if the discussion happened then.
> > >
> > > As for the comments in the other thread, I think there are only a
> > > couple of misconceptions on the proposal itself, as they are not
> > > actual problems (eg: managed ledger is not affected at all by this
> > > proposal, as the naming happens on top of it).
> > >
> > > Some parts can be clarified (as it is always the case), though I don't
> > > think it's a good idea to stop a vote at this point.
> > >
> > >
> > > Matteo
> > >
> > > --
> > > Matteo Merli
> > > 
> > >
> > >
> > > On Mon, May 2, 2022 at 3:31 AM Lari Hotari  wrote:
> > > >
> > > > -1. It's too early to start a vote. Let's first have discussions.
> > > >
> > > > -Lari
> > > >
> > > > ma 2. toukok. 2022 klo 9.50 Andras Beni  .invalid>
> > > > kirjoitti:
> > > >
> > > > > Hi Pulsar Community,
> > > > >
> > > > > I would like to start a VOTE on "Bucketing topic metadata to allow
> more
> > > > > topics per namespace" (PIP-157).
> > > > >
> > > > > The proposal can be read at
> https://github.com/apache/pulsar/issues/15254
> > > > > and the discussion thead is available at
> > > > > https://lists.apache.org/thread/zx6s7hyrl2vy7nhdl79wh6gn88kxpd6k.
> > > > >
> > > > > Voting will stay open for at least 48h.
> > > > >
> > > > > Thanks,
> > > > > Andras
> > > > >
>

Re: [VOTE] PIP-157: Bucketing topic metadata to allow more topics per namespace

[Enrico Olivelli]

+1 (binding)

Enrico

Il giorno mer 18 mag 2022 alle ore 08:54 Matteo Merli
 ha scritto:
>
> +1
>
> --
> Matteo Merli
> 
>
> On Mon, May 2, 2022 at 6:40 PM Matteo Merli  wrote:
> >
> > Lari & Enrico, the discussion thread was out for 11 days and there
> > were 2 positive feedbacks.
> > I don't think this qualifies as "too early for a vote" and it would
> > have been better if the discussion happened then.
> >
> > As for the comments in the other thread, I think there are only a
> > couple of misconceptions on the proposal itself, as they are not
> > actual problems (eg: managed ledger is not affected at all by this
> > proposal, as the naming happens on top of it).
> >
> > Some parts can be clarified (as it is always the case), though I don't
> > think it's a good idea to stop a vote at this point.
> >
> >
> > Matteo
> >
> > --
> > Matteo Merli
> > 
> >
> >
> > On Mon, May 2, 2022 at 3:31 AM Lari Hotari  wrote:
> > >
> > > -1. It's too early to start a vote. Let's first have discussions.
> > >
> > > -Lari
> > >
> > > ma 2. toukok. 2022 klo 9.50 Andras Beni 
> > > 
> > > kirjoitti:
> > >
> > > > Hi Pulsar Community,
> > > >
> > > > I would like to start a VOTE on "Bucketing topic metadata to allow more
> > > > topics per namespace" (PIP-157).
> > > >
> > > > The proposal can be read at 
> > > > https://github.com/apache/pulsar/issues/15254
> > > > and the discussion thead is available at
> > > > https://lists.apache.org/thread/zx6s7hyrl2vy7nhdl79wh6gn88kxpd6k.
> > > >
> > > > Voting will stay open for at least 48h.
> > > >
> > > > Thanks,
> > > > Andras
> > > >

Re: [VOTE] PIP-157: Bucketing topic metadata to allow more topics per namespace

[Matteo Merli]

+1

--
Matteo Merli


On Mon, May 2, 2022 at 6:40 PM Matteo Merli  wrote:
>
> Lari & Enrico, the discussion thread was out for 11 days and there
> were 2 positive feedbacks.
> I don't think this qualifies as "too early for a vote" and it would
> have been better if the discussion happened then.
>
> As for the comments in the other thread, I think there are only a
> couple of misconceptions on the proposal itself, as they are not
> actual problems (eg: managed ledger is not affected at all by this
> proposal, as the naming happens on top of it).
>
> Some parts can be clarified (as it is always the case), though I don't
> think it's a good idea to stop a vote at this point.
>
>
> Matteo
>
> --
> Matteo Merli
> 
>
>
> On Mon, May 2, 2022 at 3:31 AM Lari Hotari  wrote:
> >
> > -1. It's too early to start a vote. Let's first have discussions.
> >
> > -Lari
> >
> > ma 2. toukok. 2022 klo 9.50 Andras Beni 
> > 
> > kirjoitti:
> >
> > > Hi Pulsar Community,
> > >
> > > I would like to start a VOTE on "Bucketing topic metadata to allow more
> > > topics per namespace" (PIP-157).
> > >
> > > The proposal can be read at https://github.com/apache/pulsar/issues/15254
> > > and the discussion thead is available at
> > > https://lists.apache.org/thread/zx6s7hyrl2vy7nhdl79wh6gn88kxpd6k.
> > >
> > > Voting will stay open for at least 48h.
> > >
> > > Thanks,
> > > Andras
> > >

Re: [VOTE] PIP-161 Exclusive Producer: new mode ExclusiveWithFencing

[Enrico Olivelli]

The PIP passes with 3 bindings +1: Enrico, Matteo and Lari.

I will rebase the patch and commit it (it has already been reviewed)

Thank you very much

Enrico

Il giorno mer 18 mag 2022 alle ore 08:51 Lari Hotari
 ha scritto:
>
> +1
>
> -Lari
>
> On 2022/05/16 07:09:19 Enrico Olivelli wrote:
> > This is the VOTE thread for PIP-161
> >
> > This is the GH issue: https://github.com/apache/pulsar/issues/15528
> > This is the PR: https://github.com/apache/pulsar/pull/15488
> >
> > Motivation
> >
> > In PIP-68 we introduced two access modes for the Producer:
> >
> > Exclusive: The producer is the only one who can publish to the topic.
> > Fail if there is another Exclusive Producer connected to the topic
> > while creating the new Producer.
> > WaitForExclusive: Like Exclusive, but instead of Failing we are going
> > to wait for the current Exclusive Producer to disconnect.
> >
> > Those two modes are very powerful and allow you to perform some kind
> > of Locking on a topic.
> >
> > We are missing a third more, in which the Producer always succeeds to
> > acquire the Exclusive lock on the topic by fencing out any other
> > Producer that is connected, even the current Exclusive Producer and
> > the other Producers waiting in WaitForExclusive mode.
> >
> > Goal
> >
> > The modes that are available with PIP-68 require a writer to acquire
> > the lock and release it as soon as possible in order to allow other
> > clients to write to the topic.
> >
> > With the new mode it will be possible to implement locking in another
> > way: the Producer holds the lock until someone else steals it. This
> > way when you have very low contention you can achieve better latency
> > for writes because you don't have to acquire the lock every time you
> > want to write,.
> >
> > API and Wire protocol Changes
> >
> > Changes:
> >
> > a new constant on the Wire Protocol for AccessMode
> > a new constant in the Java Client API AccessMode#ExclusiveWithFencing
> >
> > Implementation
> >
> > The new mode will behave mostly like AccessMode#Exclusive but instead
> > of failing in case of the presence of other Producers it will force
> > all of the current connected Producers to be removed and invalidated
> > (they will see ProducerFencedException).
> >
> > Reject Alternatives
> >
> > None
> >
> > Enrico
> >

Re: [VOTE] PIP-161 Exclusive Producer: new mode ExclusiveWithFencing

[Lari Hotari]

+1

-Lari

On 2022/05/16 07:09:19 Enrico Olivelli wrote:
> This is the VOTE thread for PIP-161
> 
> This is the GH issue: https://github.com/apache/pulsar/issues/15528
> This is the PR: https://github.com/apache/pulsar/pull/15488
> 
> Motivation
> 
> In PIP-68 we introduced two access modes for the Producer:
> 
> Exclusive: The producer is the only one who can publish to the topic.
> Fail if there is another Exclusive Producer connected to the topic
> while creating the new Producer.
> WaitForExclusive: Like Exclusive, but instead of Failing we are going
> to wait for the current Exclusive Producer to disconnect.
> 
> Those two modes are very powerful and allow you to perform some kind
> of Locking on a topic.
> 
> We are missing a third more, in which the Producer always succeeds to
> acquire the Exclusive lock on the topic by fencing out any other
> Producer that is connected, even the current Exclusive Producer and
> the other Producers waiting in WaitForExclusive mode.
> 
> Goal
> 
> The modes that are available with PIP-68 require a writer to acquire
> the lock and release it as soon as possible in order to allow other
> clients to write to the topic.
> 
> With the new mode it will be possible to implement locking in another
> way: the Producer holds the lock until someone else steals it. This
> way when you have very low contention you can achieve better latency
> for writes because you don't have to acquire the lock every time you
> want to write,.
> 
> API and Wire protocol Changes
> 
> Changes:
> 
> a new constant on the Wire Protocol for AccessMode
> a new constant in the Java Client API AccessMode#ExclusiveWithFencing
> 
> Implementation
> 
> The new mode will behave mostly like AccessMode#Exclusive but instead
> of failing in case of the presence of other Producers it will force
> all of the current connected Producers to be removed and invalidated
> (they will see ProducerFencedException).
> 
> Reject Alternatives
> 
> None
> 
> Enrico
> 

[GitHub] [pulsar-site] urfreespace merged pull request #80: Add bookies command to pulsar-admin cli documentation page

[GitBox]

urfreespace merged PR #80:
URL: https://github.com/apache/pulsar-site/pull/80


-- 
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-site] urfreespace merged pull request #82: fix filter

[GitBox]

urfreespace merged PR #82:
URL: https://github.com/apache/pulsar-site/pull/82


-- 
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-site] zrsaber opened a new pull request, #82: fix filter

[GitBox]

zrsaber opened a new pull request, #82:
URL: https://github.com/apache/pulsar-site/pull/82

   Fix filter being overwritten
   
![image](https://user-images.githubusercontent.com/40480634/168974359-9f7bc3f5-871c-42b8-9e12-5dca67eaa924.png)
   
![image](https://user-images.githubusercontent.com/40480634/168974380-b843f3b0-0b22-4429-8acf-543a3f830857.png)


-- 
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: [VOTE] PIP-161 Exclusive Producer: new mode ExclusiveWithFencing

[Enrico Olivelli]

+1 (binding)

Enrico

Il giorno mar 17 mag 2022 alle ore 09:27 Matteo Merli
 ha scritto:
>
> +1
> --
> Matteo Merli
> 
>
> On Mon, May 16, 2022 at 9:09 AM Enrico Olivelli  wrote:
> >
> > This is the VOTE thread for PIP-161
> >
> > This is the GH issue: https://github.com/apache/pulsar/issues/15528
> > This is the PR: https://github.com/apache/pulsar/pull/15488
> >
> > Motivation
> >
> > In PIP-68 we introduced two access modes for the Producer:
> >
> > Exclusive: The producer is the only one who can publish to the topic.
> > Fail if there is another Exclusive Producer connected to the topic
> > while creating the new Producer.
> > WaitForExclusive: Like Exclusive, but instead of Failing we are going
> > to wait for the current Exclusive Producer to disconnect.
> >
> > Those two modes are very powerful and allow you to perform some kind
> > of Locking on a topic.
> >
> > We are missing a third more, in which the Producer always succeeds to
> > acquire the Exclusive lock on the topic by fencing out any other
> > Producer that is connected, even the current Exclusive Producer and
> > the other Producers waiting in WaitForExclusive mode.
> >
> > Goal
> >
> > The modes that are available with PIP-68 require a writer to acquire
> > the lock and release it as soon as possible in order to allow other
> > clients to write to the topic.
> >
> > With the new mode it will be possible to implement locking in another
> > way: the Producer holds the lock until someone else steals it. This
> > way when you have very low contention you can achieve better latency
> > for writes because you don't have to acquire the lock every time you
> > want to write,.
> >
> > API and Wire protocol Changes
> >
> > Changes:
> >
> > a new constant on the Wire Protocol for AccessMode
> > a new constant in the Java Client API AccessMode#ExclusiveWithFencing
> >
> > Implementation
> >
> > The new mode will behave mostly like AccessMode#Exclusive but instead
> > of failing in case of the presence of other Producers it will force
> > all of the current connected Producers to be removed and invalidated
> > (they will see ProducerFencedException).
> >
> > Reject Alternatives
> >
> > None
> >
> > Enrico

Re: [DISCUSS] PIP-167: Make it Configurable to Require Subscription Permission

[Enrico Olivelli]

The proposal makes sense to me.

+1

Enrico

Il giorno mer 18 mag 2022 alle ore 07:18 Michael Marshall
 ha scritto:
>
> I switched to the name "permissionOnSubscriptionRequired" for this
> feature [0]. It describes the feature while satisfying the requirement
> to default to false.
>
> I plan to address the PR's remaining feedback and write tests tomorrow
> (Wednesday). If there isn't any other discussion, I'll start the vote
> once I get tests passing.
>
> Thanks,
> Michael
>
> [0] https://github.com/apache/pulsar/pull/15576
>
> On Fri, May 13, 2022 at 2:53 PM Michael Marshall  wrote:
> >
> > Hello Pulsar Community,
> >
> > Here is a PIP to add a new namespace policy to configure how the
> > PulsarAuthorizationProvider handles the default subscription
> > permission value (null/an empty set). I look forward to your feedback.
> >
> > PIP: https://github.com/apache/pulsar/issues/15597
> >
> > Thanks,
> > Michael
> >
> > ## Motivation
> >
> > Pulsar supports subscription level authorization. When combined with
> > topic level authorization, a user can configure Pulsar to limit which
> > roles can consume from which topic subscriptions. However, when this
> > feature is left unconfigured for a subscription, a role that has
> > permission to consume from a topic is, by default, implicitly granted
> > permission to consume from any subscription on that topic. As a
> > consequence, a missed security configuration could lead to accidental
> > privilege escalation. Here is a reference to the code responsible for
> > the current behavior:
> >
> > https://github.com/apache/pulsar/blob/6864b0ae5520e06b9d0fc5dcfa5a0a0a44feee87/pulsar-broker-common/src/main/java/org/apache/pulsar/broker/authorization/PulsarAuthorizationProvider.java#L115-L122
> >
> > ## Goal
> >
> > I propose we add a namespace policy to configure a Pulsar namespace to
> > either allow all or reject all roles when there is no configuration
> > for a specific subscription’s permission. This way, a missed
> > configuration results in a rejected request due to insufficient
> > permission.
> >
> > This PIP will not change the current behavior and will be backwards
> > compatible. It will add a new boolean field to the existing
> > `auth_policies` namespace policy to configure how the
> > `PulsarAuthorizationProvider` handles an empty set of allowed roles in
> > the `canConsume` method.
> >
> > ## Naming
> >
> > I am not settled on the right name for this feature/namespace policy
> > yet. Hopefully this thread can help identify the right name.
> >
> > First, the existing subscription level authorization feature has
> > several names. The Admin API calls this feature
> > `PermissionOnSubscription`, the Pulsar Admin CLI tool calls it
> > `subscription-permission`, the AuthPolicies interface calls it
> > `SubscriptionAuthentication`, and the value is stored in the metadata
> > store as `subscription_auth_roles`.
> >
> > My preferred names for this feature are `implicit_subscription_auth`
> > and `implicitPermissionOnSubscription` because they work well with the
> > “grant” and “revoke” actions, e.g.
> > `grantImplicitPermissionOnSubscription` would be a PUT/POST call to
> > the `/implicitPermissionOnSubscription` endpoint to set the policy
> > value to true. However, that policy name requires the default value to
> > be true to maintain backwards compatibility. Enrico expressed concern
> > that defaulting to true is problematic for the upgrade path:
> > https://github.com/apache/pulsar/pull/15576#discussion_r872045946.
> >
> > Alternatively, we could use the names
> > `PermissionOnSubscriptionRequired` and `subscription_auth_required`.
> > In that case, I would switch the admin API so that the admin API has a
> > single setter endpoint that takes the configuration as a part of the
> > body instead of relying on PUT to mean grant permission and DELETE to
> > mean revoke permission.
> >
> > Please let me know if you have thoughts on what name(s) make sense for
> > this feature.
> >
> > ## API Changes
> >
> > The API changes include updating the Admin API to enable getting and
> > modifying the namespace policy, as well as updating the namespace
> > AuthPolicy interface to store this new metadata field.
> >
> > ## Implementation
> >
> > Draft implementation: https://github.com/apache/pulsar/pull/15576
> >
> > The core update is to the
> > `PulsarAuthorizationProvider#canConsumeAsync` method so that when
> > `implicit_subscription_auth` is true, a null or empty set of roles for
> > a subscription’s permission will result in granted permission to
> > consume from the subscription, and when `implicit_subscription_auth`
> > is false, a null or empty set of roles for a subscription’s permission
> > will result in rejected permission to consume from the subscription.
> > Note that if we negate the meaning of the variable name, the logic
> > will also be inverted appropriately.
> >
> > ## Rejected Alternatives
> >
> > First, we have already received a PR proposing to