[GitHub] [pulsar-site] Anonymitaet opened a new pull request, #58: [feature][doc] Add multiple release notes for Pulsar and Client

[GitBox]

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

   Preview looks good:
   https://user-images.githubusercontent.com/50226895/165278467-b2ce9888-cde9-4b38-abff-605830f74253.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

[GitHub] [pulsar-helm-chart] youg9203 commented on issue #78: Metrics from pulsar proxy are not scraped because /metrics when authentication is enabled

[GitBox]

youg9203 commented on issue #78:
URL: 
https://github.com/apache/pulsar-helm-chart/issues/78#issuecomment-1109664517

   > ```yaml
   > 
   > PULSAR_PREFIX_authenticateMetricsEndpoint: "false"
   > ```
   I need to understand if this parameter is working? Or did you just provide 
the suggestion for the solution?
   
   I'm also facing this issue now, love to hear any other way to fix the 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

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

[guo jiwei]

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
,
we support topic policy to replicate across clusters and release in Pulsar
2.10.

And with version iteration, the corresponding topic policy CLI and
functions are mature and stable, but users need to enable system topic to
support these features.  So it's better to enable system topic by default.


So I have opened apache/pulsar#15333
 to discuss this.


Regards
Jiwei Guo (Tboy)

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

[Enrico Olivelli]

Which are the downsides of enabling system topics?

Enrico

Il Mar 26 Apr 2022, 14:07 guo jiwei  ha scritto:

> 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
> <
> https://github.com/apache/pulsar/wiki/PIP-92%3A-Topic-policy-across-multiple-clusters
> >,
> we support topic policy to replicate across clusters and release in Pulsar
> 2.10.
>
> And with version iteration, the corresponding topic policy CLI and
> functions are mature and stable, but users need to enable system topic to
> support these features.  So it's better to enable system topic by default.
>
>
> So I have opened apache/pulsar#15333
>  to discuss this.
>
>
> Regards
> Jiwei Guo (Tboy)
>

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

[Zike Yang]

+1

Please update this PIP number. It's duplicated with
https://github.com/apache/pulsar/issues/15207

Zike

On Tue, Apr 26, 2022 at 8:09 PM Enrico Olivelli  wrote:
>
> Which are the downsides of enabling system topics?
>
> Enrico
>
> Il Mar 26 Apr 2022, 14:07 guo jiwei  ha scritto:
>
> > 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
> > <
> > https://github.com/apache/pulsar/wiki/PIP-92%3A-Topic-policy-across-multiple-clusters
> > >,
> > we support topic policy to replicate across clusters and release in Pulsar
> > 2.10.
> >
> > And with version iteration, the corresponding topic policy CLI and
> > functions are mature and stable, but users need to enable system topic to
> > support these features.  So it's better to enable system topic by default.
> >
> >
> > So I have opened apache/pulsar#15333
> >  to discuss this.
> >
> >
> > Regards
> > Jiwei Guo (Tboy)
> >

[GitHub] [pulsar-helm-chart] michaeljmarshall commented on issue #78: Metrics from pulsar proxy are not scraped because /metrics when authentication is enabled

[GitBox]

michaeljmarshall commented on issue #78:
URL: 
https://github.com/apache/pulsar-helm-chart/issues/78#issuecomment-1110029405

   > > ```yaml
   > > PULSAR_PREFIX_authenticateMetricsEndpoint: "false"
   > > ```
   > 
   > I need to understand, is this parameter is working? Or did you just 
provide the suggestion for the solution?
   > 
   > I'm also facing this issue now, and love to hear any other way to fix the 
issue.
   
   Yes, this is the correct solution. Whenever a configuration is not present 
in the `conf/proxy.conf` (or any of the `.conf` files), you must add the 
`PULSAR_PREFIX_` to the start of the configuration value. By doing so, the 
configuration script will map the suffix into the `.conf` file.
   
   
https://github.com/apache/pulsar/blob/0c694cfdc9b11f915f1da86260ad3655c2e99a35/docker/pulsar/scripts/apply-config-from-env.py#L37
   
   Note that in the case of functions, the prefix is actually `PF_`. Note that 
the worker config files are `.yml`.
   
   
https://github.com/apache/pulsar/blob/0c694cfdc9b11f915f1da86260ad3655c2e99a35/docker/pulsar/scripts/gen-yml-from-env.py#L55
   
   You can see here that we run the `bin/apply-config-from-env.py` script 
before starting the proxy process.
   
   
https://github.com/apache/pulsar-helm-chart/blob/cee3fcfe569e2a8cc87fb5f8046b29f47f1d4e39/charts/pulsar/templates/proxy-statefulset.yaml#L184
   
   If you'd like to avoid adding the `PULSAR_PREFIX_`, the best solution is to 
open a PR in the apache/pulsar project and add the config, in this case 
`authenticateMetricsEndpoint` to the proxy conf. Then, a prefix won't be needed 
for this specific 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

[GitHub] [pulsar-site] DaveDuggins closed pull request #52: Updated sidebar label tags

[GitBox]

DaveDuggins closed pull request #52: Updated sidebar label tags
URL: https://github.com/apache/pulsar-site/pull/52


-- 
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] DaveDuggins closed pull request #59: Apache main

[GitBox]

DaveDuggins closed pull request #59: Apache main
URL: https://github.com/apache/pulsar-site/pull/59


-- 
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: [DISCUSSION] PIP-156: Enable system topic by default

[PengHui Li]

> Which are the downsides of enabling system topics?

No obvious downsides, just created a __change_events topic under each
namespace
and the broker created a reader to read new messages from it. Looks like
introducing some
idle topics and idle readers if users will not use the topic policy.

And transactions will also need the system topic feature.

Penghui

On Tue, Apr 26, 2022 at 10:27 PM Zike Yang  wrote:

> +1
>
> Please update this PIP number. It's duplicated with
> https://github.com/apache/pulsar/issues/15207
>
> Zike
>
> On Tue, Apr 26, 2022 at 8:09 PM Enrico Olivelli 
> wrote:
> >
> > Which are the downsides of enabling system topics?
> >
> > Enrico
> >
> > Il Mar 26 Apr 2022, 14:07 guo jiwei  ha scritto:
> >
> > > Hi community:
> > >In PIP-39
> > > <
> https://github.com/apache/pulsar/wiki/PIP-39%3A-Namespace-Change-Events>,
> > > we have introduced namespace event to support topic level policy. This
> > > feature was released in Pulsar 2.6.
> > >
> > >Then PIP-92
> > > <
> > >
> https://github.com/apache/pulsar/wiki/PIP-92%3A-Topic-policy-across-multiple-clusters
> > > >,
> > > we support topic policy to replicate across clusters and release in
> Pulsar
> > > 2.10.
> > >
> > > And with version iteration, the corresponding topic policy CLI and
> > > functions are mature and stable, but users need to enable system topic
> to
> > > support these features.  So it's better to enable system topic by
> default.
> > >
> > >
> > > So I have opened apache/pulsar#15333
> > >  to discuss this.
> > >
> > >
> > > Regards
> > > Jiwei Guo (Tboy)
> > >
>

[ANNOUNCE] New Committer: Nicolò Boschi

[PengHui Li]

The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
Boschi
https://github.com/nicoloboschi to become a committer and we are pleased to
announce that he has accepted.

Welcome and Congratulations, Nicolò Boschi

Please join us in congratulating and welcoming Nicolò Boschi onboard!

Best Regards,
Penghui Li on behalf of the Pulsar PMC

[GitHub] [pulsar-site] urfreespace merged pull request #58: [feature][doc] Add multiple release notes for Pulsar and Client

[GitBox]

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


-- 
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: [ANNOUNCE] New Committer: Nicolò Boschi

[Yu]

Congrats Nicolò!

On Wed, Apr 27, 2022 at 7:48 AM PengHui Li  wrote:

> The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> Boschi
> https://github.com/nicoloboschi to become a committer and we are pleased
> to
> announce that he has accepted.
>
> Welcome and Congratulations, Nicolò Boschi
>
> Please join us in congratulating and welcoming Nicolò Boschi onboard!
>
> Best Regards,
> Penghui Li on behalf of the Pulsar PMC
>

Re: [ANNOUNCE] New Committer: Nicolò Boschi

[Christophe Bornet]

Congratulations Nicolo !

Le mar. 26 avr. 2022 à 19:48, PengHui Li  a écrit :

> The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> Boschi
> https://github.com/nicoloboschi to become a committer and we are pleased
> to
> announce that he has accepted.
>
> Welcome and Congratulations, Nicolò Boschi
>
> Please join us in congratulating and welcoming Nicolò Boschi onboard!
>
> Best Regards,
> Penghui Li on behalf of the Pulsar PMC
>

Re: [ANNOUNCE] New Committer: Nicolò Boschi

[Haiting Jiang]

Congrats!

BR,
Haiting

On 2022/04/26 23:48:25 PengHui Li wrote:
> The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> Boschi
> https://github.com/nicoloboschi to become a committer and we are pleased to
> announce that he has accepted.
> 
> Welcome and Congratulations, Nicolò Boschi
> 
> Please join us in congratulating and welcoming Nicolò Boschi onboard!
> 
> Best Regards,
> Penghui Li on behalf of the Pulsar PMC
> 

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

[Haiting Jiang]

+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 level policy. This
> feature was released in Pulsar 2.6.
> 
>Then PIP-92
> ,
> we support topic policy to replicate across clusters and release in Pulsar
> 2.10.
> 
> And with version iteration, the corresponding topic policy CLI and
> functions are mature and stable, but users need to enable system topic to
> support these features.  So it's better to enable system topic by default.
> 
> 
> So I have opened apache/pulsar#15333
>  to discuss this.
> 
> 
> Regards
> Jiwei Guo (Tboy)
> 

Re: [VOTE] [PIP-154] Max active transaction limitation for transaction coordinator

[Haiting Jiang]

+1

Thanks,
Haiting

On 2022/04/24 02:00:39 丛搏 wrote:
> Hi Pulsar community,
> 
> This is the voting thread for PIP-154. It will stay open for at least 48 
> hours.
> 
> The proposal can be found: https://github.com/apache/pulsar/issues/15133
> 
> Discuss thread: 
> https://lists.apache.org/thread/h8gzgs78bm4pzy2rjtgvvmo1jbzttcx8
> 
> Thanks,
> Bo
> 

Re: [VOTE] PIP-155: Drop support for Python2

[Lin Lin]

+1

Lin Lin

Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

[Lin Lin]

+1

Lin Lin

Re: [VOTE] [PIP-154] Max active transaction limitation for transaction coordinator

[Jiuming Tao]

+1
Thanks,
Tao Jiuming

> 2022年4月24日 上午10:00，丛搏  写道：
> 
> Hi Pulsar community,
> 
> This is the voting thread for PIP-154. It will stay open for at least 48 
> hours.
> 
> The proposal can be found: https://github.com/apache/pulsar/issues/15133
> 
> Discuss thread: 
> https://lists.apache.org/thread/h8gzgs78bm4pzy2rjtgvvmo1jbzttcx8
> 
> Thanks,
> Bo

Re: [ANNOUNCE] New Committer: Nicolò Boschi

[Michael Marshall]

Congratulations, Nicolò!

- Michael

On Tue, Apr 26, 2022 at 9:39 PM Haiting Jiang  wrote:
>
> Congrats!
>
> BR,
> Haiting
>
> On 2022/04/26 23:48:25 PengHui Li wrote:
> > The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> > Boschi
> > https://github.com/nicoloboschi to become a committer and we are pleased to
> > announce that he has accepted.
> >
> > Welcome and Congratulations, Nicolò Boschi
> >
> > Please join us in congratulating and welcoming Nicolò Boschi onboard!
> >
> > Best Regards,
> > Penghui Li on behalf of the Pulsar PMC
> >

Re: [ANNOUNCE] New Committer: Nicolò Boschi

[ZhangJian He]

Congratulations, Nicolò!

Thanks
ZhangJian He

Michael Marshall  于2022年4月27日周三 11:24写道：

> Congratulations, Nicolò!
>
> - Michael
>
> On Tue, Apr 26, 2022 at 9:39 PM Haiting Jiang 
> wrote:
> >
> > Congrats!
> >
> > BR,
> > Haiting
> >
> > On 2022/04/26 23:48:25 PengHui Li wrote:
> > > The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> > > Boschi
> > > https://github.com/nicoloboschi to become a committer and we are
> pleased to
> > > announce that he has accepted.
> > >
> > > Welcome and Congratulations, Nicolò Boschi
> > >
> > > Please join us in congratulating and welcoming Nicolò Boschi onboard!
> > >
> > > Best Regards,
> > > Penghui Li on behalf of the Pulsar PMC
> > >
>

Re: [ANNOUNCE] New Committer: Nicolò Boschi

[Hang Chen]

Congrats, Nicolò!

Best,
Hang

ZhangJian He  于2022年4月27日周三 11:35写道：
>
> Congratulations, Nicolò!
>
> Thanks
> ZhangJian He
>
> Michael Marshall  于2022年4月27日周三 11:24写道：
>
> > Congratulations, Nicolò!
> >
> > - Michael
> >
> > On Tue, Apr 26, 2022 at 9:39 PM Haiting Jiang 
> > wrote:
> > >
> > > Congrats!
> > >
> > > BR,
> > > Haiting
> > >
> > > On 2022/04/26 23:48:25 PengHui Li wrote:
> > > > The Apache Pulsar Project Management Committee (PMC) has invited Nicolò
> > > > Boschi
> > > > https://github.com/nicoloboschi to become a committer and we are
> > pleased to
> > > > announce that he has accepted.
> > > >
> > > > Welcome and Congratulations, Nicolò Boschi
> > > >
> > > > Please join us in congratulating and welcoming Nicolò Boschi onboard!
> > > >
> > > > Best Regards,
> > > > Penghui Li on behalf of the Pulsar PMC
> > > >
> >

Re: [ANNOUNCE] New Committer: Nicolò Boschi

[Enrico Olivelli]

Congratulations !

Enrico

Il giorno mer 27 apr 2022 alle ore 05:40 Hang Chen
 ha scritto:
>
> Congrats, Nicolò!
>
> Best,
> Hang
>
> ZhangJian He  于2022年4月27日周三 11:35写道：
> >
> > Congratulations, Nicolò!
> >
> > Thanks
> > ZhangJian He
> >
> > Michael Marshall  于2022年4月27日周三 11:24写道：
> >
> > > Congratulations, Nicolò!
> > >
> > > - Michael
> > >
> > > On Tue, Apr 26, 2022 at 9:39 PM Haiting Jiang 
> > > wrote:
> > > >
> > > > Congrats!
> > > >
> > > > BR,
> > > > Haiting
> > > >
> > > > On 2022/04/26 23:48:25 PengHui Li wrote:
> > > > > The Apache Pulsar Project Management Committee (PMC) has invited 
> > > > > Nicolò
> > > > > Boschi
> > > > > https://github.com/nicoloboschi to become a committer and we are
> > > pleased to
> > > > > announce that he has accepted.
> > > > >
> > > > > Welcome and Congratulations, Nicolò Boschi
> > > > >
> > > > > Please join us in congratulating and welcoming Nicolò Boschi onboard!
> > > > >
> > > > > Best Regards,
> > > > > Penghui Li on behalf of the Pulsar PMC
> > > > >
> > >

[GitHub] [pulsar-client-node] dependabot[bot] opened a new pull request, #210: Bump grunt from 1.4.1 to 1.5.2

[GitBox]

dependabot[bot] opened a new pull request, #210:
URL: https://github.com/apache/pulsar-client-node/pull/210

   Bumps [grunt](https://github.com/gruntjs/grunt) from 1.4.1 to 1.5.2.
   
   Release notes
   Sourced from https://github.com/gruntjs/grunt/releases";>grunt's releases.
   
   v1.5.2
   
   Update Changelog  7f15fd5
   Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1743";>#1743
 from gruntjs/cleanup-link  b0ec6e1
   Clean up link handling  433f91b
   
   https://github.com/gruntjs/grunt/compare/v1.5.1...v1.5.2";>https://github.com/gruntjs/grunt/compare/v1.5.1...v1.5.2
   v1.5.1
   
   Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1742";>#1742
 from gruntjs/update-symlink-test  ad22608
   Fix symlink test  0652305
   
   https://github.com/gruntjs/grunt/compare/v1.5.0...v1.5.1";>https://github.com/gruntjs/grunt/compare/v1.5.0...v1.5.1
   v1.5.0
   
   Updated changelog  b2b2c2b
   Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1740";>#1740
 from gruntjs/update-deps-22-10  3eda6ae
   Update testing matrix  47d32de
   More updates  2e9161c
   Remove console log  04b960e
   Update dependencies, tests...  aad3d45
   Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1736";>#1736
 from justlep/main  fdc7056
   support .cjs extension  e35fe54
   
   https://github.com/gruntjs/grunt/compare/v1.4.1...v1.5.0";>https://github.com/gruntjs/grunt/compare/v1.4.1...v1.5.0
   
   
   
   Changelog
   Sourced from https://github.com/gruntjs/grunt/blob/main/CHANGELOG";>grunt's 
changelog.
   
   v1.5.2
   date: 2022-04-12
   changes:
   - Unlink symlinks when copy destination is a symlink.
   v1.5.1
   date: 2022-04-11
   changes:
   - Fixed symlink destination handling.
   v1.5.0
   date: 2022-04-10
   changes:
   - Updated dependencies.
   - Add symlink handling for copying files.
   
   
   
   Commits
   
   https://github.com/gruntjs/grunt/commit/ac667b24cabfff77cf769f9dbf9ddba9576b3dc2";>ac667b2
 1.5.2
   https://github.com/gruntjs/grunt/commit/7f15fd5ad9fb33ca0fe4680af7bce84d69deb673";>7f15fd5
 Update Changelog
   https://github.com/gruntjs/grunt/commit/b0ec6e12426fc8d5720dee1702f6a67455c5986c";>b0ec6e1
 Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1743";>#1743
 from gruntjs/cleanup-link
   https://github.com/gruntjs/grunt/commit/433f91b78df99d83daa6f56a5505ead743627c30";>433f91b
 Clean up link handling
   https://github.com/gruntjs/grunt/commit/d5969eccf2493c2c579c55a617c70cab48dc12d3";>d5969ec
 1.5.1
   https://github.com/gruntjs/grunt/commit/ad226080f2e1da3fc429f36926b00708ec9b403d";>ad22608
 Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1742";>#1742
 from gruntjs/update-symlink-test
   https://github.com/gruntjs/grunt/commit/0652305f1b79dfdc85a9bd0f2e78ca1e9ae795f5";>0652305
 Fix symlink test
   https://github.com/gruntjs/grunt/commit/a7ab0a83ab7e2e9ca1ab08a6a2514f5f50102b7f";>a7ab0a8
 1.5.0
   https://github.com/gruntjs/grunt/commit/b2b2c2b117ab068da86a6114705fc3c0d653f26b";>b2b2c2b
 Updated changelog
   https://github.com/gruntjs/grunt/commit/3eda6ae1180badba5b6535147296f0457f470f53";>3eda6ae
 Merge pull request https://github-redirect.dependabot.com/gruntjs/grunt/issues/1740";>#1740
 from gruntjs/update-deps-22-10
   Additional commits viewable in https://github.com/gruntjs/grunt/compare/v1.4.1...v1.5.2";>compare 
view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=grunt&package-manager=npm_and_yarn&previous-version=1.4.1&new-version=1.5.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   -