Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 (non-binding) Best, Ran On 2022/04/26 12:07:32 guo jiwei wrote: > Hi community: >In PIP-39 > , > we have introduced namespace event to support topic level policy. This > feature was released in Pulsar 2.6. > >

Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 (non-binding) Thanks, Yunze

Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 Best, Mattison On Wed, 11 May 2022 at 13:49, Qiang Zhao wrote: > > > On 2022/04/26 12:07:32 guo jiwei wrote: > > Hi community: > >In PIP-39 > > >, > > we have introduced namespace event to support topic level

Re: [DISCUSSION] PIP-156: Enable system topic by default

On 2022/04/26 12:07:32 guo jiwei wrote: > Hi community: >In PIP-39 > , > we have introduced namespace event to support topic level policy. This > feature was released in Pulsar 2.6. > >Then PIP-92 >

Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 Thanks, Bo Haiting Jiang 于2022年4月27日周三 10:39写道： > > +1 > > Thanks, > Haiting > > On 2022/04/26 12:07:32 guo jiwei wrote: > > Hi community: > >In PIP-39 > > , > > we have introduced namespace event to support topic

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1, NB Thanks for your work. Best Regards, Lan Liang On 5/10/2022 19:31，mattison chao wrote： +1 (non-binding) Best, Mattison On Tue, 10 May 2022 at 19:00, Yunze Xu wrote: +1 (non-binding) Thanks, Yunze

[GitHub] [pulsar-site] urfreespace merged pull request #73: [PIP-87][Website] Publish website from asf-site-next branch

urfreespace merged PR #73: URL: https://github.com/apache/pulsar-site/pull/73 -- 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-site] dave2wave commented on issue #72: Data driven pages - How to Submit New Content

dave2wave commented on issue #72: URL: https://github.com/apache/pulsar-site/issues/72#issuecomment-1123155868 Yes, but let me make specific suggestions in a new issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

[GitHub] [pulsar-site] Anonymitaet commented on issue #72: Data driven pages - How to Submit New Content

Anonymitaet commented on issue #72: URL: https://github.com/apache/pulsar-site/issues/72#issuecomment-1123124163 Hi @dave2wave Do you want us to make changes to the [Meet the Community](https://pulsar-next.staged.apache.org/community/#section-community) page? If so, can you explicitly

[GitHub] [pulsar-site] Anonymitaet commented on a diff in pull request #70: [improve][website] Add license explanations to Ecosystem page

Anonymitaet commented on code in PR #70: URL: https://github.com/apache/pulsar-site/pull/70#discussion_r869823108 ## site2/website-next/src/pages/ecosystem.js: ## @@ -37,7 +37,7 @@ export default function Home() { Ecosystem To

Re: [DISCUSS] PIP-157 Exclusive Producer: new mode ExclusiveWithFencing

Nice improvement. I was searching for similar functionalities to ban/fence old producers and found a similar improvement/suggestion from [PIP 68 Suggestions]( https://github.com/apache/pulsar/issues/7584) in addition to PIP 68. Best, Kezhu Wang On May 10, 2022 at 21:59:43, Enrico Olivelli

[GitHub] [pulsar-site] dave2wave opened a new issue, #72: Data driven pages - How to Submit New Content

dave2wave opened a new issue, #72: URL: https://github.com/apache/pulsar-site/issues/72 There needs to be a way for users to submit new content for these pages on these pages. The javascript files that contain this data are here -

Re: Discuss about creating partitioned topic in V1

It's already deprecated. No one is encouraged to use v1 API except for users for Pulsar 1.x that had topics created with the old namings. What I'm proposing, instead of trying to fix the inconsistencies in that API, is to disable v1 API by default and leave a configuration option to turn it on in

[ANNOUNCE] Apache BookKeeper 4.15.0 released

The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.15.0. Apache BookKeeper is a scalable, fault-tolerant, and low-latency storage service optimized for real-time workloads. It has been used for a fundamental service to build reliable services. It is also the log segment

[GitHub] [pulsar-site] dave2wave commented on a diff in pull request #70: [improve][website] Add license explanations to Ecosystem page

dave2wave commented on code in PR #70: URL: https://github.com/apache/pulsar-site/pull/70#discussion_r869360194 ## site2/website-next/src/pages/ecosystem.js: ## @@ -37,7 +37,7 @@ export default function Home() { Ecosystem To

Re: [DISCUSS] PIP-157 Exclusive Producer: new mode ExclusiveWithFencing

I have renamed this to PIP-161 (there is some mess in the wiki page) Enrico Il giorno mar 10 mag 2022 alle ore 14:56 Enrico Olivelli ha scritto: > > Hello, > I created a new PIP about a new AccessMode for the Producer. > https://github.com/apache/pulsar/issues/15528 > > This is the PR:

[DISCUSS] PIP-157 Exclusive Producer: new mode ExclusiveWithFencing

Hello, I created a new PIP about a new AccessMode for the Producer. https://github.com/apache/pulsar/issues/15528 This is the PR: https://github.com/apache/pulsar/pull/15488 Honestly I don't like the name "ExclusiveWithFencing", any suggestion is really appreciated. Enrico Motivation In

[GitHub] [pulsar-site] urfreespace merged pull request #71: feat: update docker build image

urfreespace merged PR #71: URL: https://github.com/apache/pulsar-site/pull/71 -- 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-site] urfreespace opened a new pull request, #71: feat: update docker build image

urfreespace opened a new pull request, #71: URL: https://github.com/apache/pulsar-site/pull/71 Signed-off-by: Li Li -- 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

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1 (non-binding) Best, Mattison On Tue, 10 May 2022 at 19:00, Yunze Xu wrote: > +1 (non-binding) > > Thanks, > Yunze >

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1 (non-binding) Thanks, Yunze

[GitHub] [pulsar-dotpulsar] jonclare commented on pull request #97: Add crude first version of DLQ

jonclare commented on PR #97: URL: https://github.com/apache/pulsar-dotpulsar/pull/97#issuecomment-1122235167 @blankensteiner My understanding is that this would all be driven from a negative acknowledgement on a message and that the behaviour of the 'retryLetterTopic' and

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1 (binding) Penghui On Tue, May 10, 2022 at 4:47 PM Enrico Olivelli wrote: > +1 (binding) > > Enrico > > Il giorno mar 10 mag 2022 alle ore 10:46 Zixuan Liu > ha scritto: > > > > Hi Pulsar community, > > > > Voting for https://github.com/apache/pulsar/issues/15289 > > > > Discussion thread:

[GitHub] [pulsar-site] Anonymitaet opened a new pull request, #70: [improve][website] Add license explanations to Ecosystem page

Anonymitaet opened a new pull request, #70: URL: https://github.com/apache/pulsar-site/pull/70 Preview looks good: https://user-images.githubusercontent.com/50226895/167595487-870659ee-7693-486c-a279-68969b641ffc.png;> -- This is an automated message from the Apache Git Service. To

Re: [VOTE] [PIP-158] Split client TLS transport encryption from authentication

+1 (binding) Enrico Il giorno mar 10 mag 2022 alle ore 10:46 Zixuan Liu ha scritto: > > Hi Pulsar community, > > Voting for https://github.com/apache/pulsar/issues/15289 > > Discussion thread: > https://lists.apache.org/thread/fblmm8oc7h907cfnppvk71o2cbp5mk8q > > Thanks, > Zixuan > > -- > >

[VOTE] [PIP-158] Split client TLS transport encryption from authentication

Hi Pulsar community, Voting for https://github.com/apache/pulsar/issues/15289 Discussion thread: https://lists.apache.org/thread/fblmm8oc7h907cfnppvk71o2cbp5mk8q Thanks, Zixuan -- ## Motivation The client supports TLS transport encryption and TLS authentication, this code so like:

[GitHub] [pulsar-site] urfreespace merged pull request #69: fix: python api sync

urfreespace merged PR #69: URL: https://github.com/apache/pulsar-site/pull/69 -- 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-site] urfreespace opened a new pull request, #69: fix: python api sync

urfreespace opened a new pull request, #69: URL: https://github.com/apache/pulsar-site/pull/69 * python api docs build workflow changed, here are the Prs: * https://github.com/apache/pulsar/pull/14788 * https://github.com/apache/pulsar/pull/14835 *

[GitHub] [pulsar-helm-chart] benlongo commented on pull request #205: Tiered Storage config

benlongo commented on PR #205: URL: https://github.com/apache/pulsar-helm-chart/pull/205#issuecomment-1121983501 If needed I can open a new PR with this rebased. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [pulsar-dotpulsar] blankensteiner commented on pull request #97: Add crude first version of DLQ

blankensteiner commented on PR #97: URL: https://github.com/apache/pulsar-dotpulsar/pull/97#issuecomment-1121982695 Hi @GeroL Let's start with a description of the feature before diving into the current implementation. How should this work? How is DotPulsar made aware that something

[VOTE] Pulsar Manager Release 0.3.0 Candidate 3

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