Re: [VOTE] [PIP-152] Support subscription level dispatch rate limiter setting.

[Lin Lin]

+1

Lin Lin

On 2022/04/19 03:27:39 Haiting Jiang wrote:
> Hi Pulsar community,
> 
> This is the voting thread for PIP-152. It will stay open for at least 48 
> hours.
> 
> The proposal can be found: https://github.com/apache/pulsar/issues/15094
> 
> Discuss thread: 
> https://lists.apache.org/thread/r6dzr09lc42yh79vt0dvmvlv6wtz2czn
> 
> Thanks,
> Haiting Jiang
> 

Re: Revote: Pulsar website concepts

[Aaron Williams]

Thank you Melissa, et al! The site looks great and looking forward to it
being live.

Aaron Williams

On Fri, Apr 22, 2022, 11:13 AM Melissa Logan  wrote:

> Update on the Pulsar website launch: we're getting very close.
>
> The group in the #website channel is Slack is taking a final look at the
> ecosystem and docs pages. We will soon have a launch date to share.
>
> Thanks to all who provided input via the survey Yu shared a few weeks ago.
> (1) Note: There was a Docusaurus update that caused breaking changes during
> that time, so some of you noticed odd behaviors on the site which have
> since been resolved. You can preview the new site here --
> https://pulsar-next.staged.apache.org/ -- but keep in mind there are PRs
> that haven't been committed (2) and syncing issues that will resolve.
>
> If you see any red flags NOT already noted in the PR or weekly status doc
> (3), please let us know here or on #website channel by April 29. Much
> appreciated.
>
> (1) https://lists.apache.org/thread/ndrkkcm5s8xojxsgbn8wg4j1kxj37wqj
> (2) https://github.com/apache/pulsar-site/pull/53
> (3)
>
> https://docs.google.com/document/d/1QtkqXMxhF8pqfJcdkep4Wd7mm1HlQquUEkwQwHC67t8/edit#
>
> On Fri, Dec 10, 2021 at 9:58 AM Melissa Logan 
> wrote:
>
> > For record-keeping, we have added a new PIP that captures details for the
> > website design/content project:
> > https://github.com/apache/pulsar/issues/13235
> >
> > Anonymitaet, it references we'll collaborate with you and others on the
> > work being done for PIP 87. I plan to start a website channel in Slack to
> > aid in our collaboration.
> >
> > Any questions, please let me know. Thanks!
> >
> > Melissa
> >
> >
> > On Wed, Nov 3, 2021 at 7:57 PM Anonymitaet _ 
> > wrote:
> >
> >> Hi Melissa, thanks for your proposal!
> >>
> >> Hi community, as discussed before1, we're performing these tasks:
> >>
> >>- Upgrading the Pulsar website framework2. We're making progress
> >>every week. You can check the details and progress here3.
> >>- Designing the information architecture4. Since it is a large
> >>project, we need more time to design and will send out the proposal
> later.
> >>
> >> Feel free to comment, thanks.
> >>
> >> 1: https://lists.apache.org/thread/39ct84dlxbo6zf0kktm15pyc7fd1n8cc
> >> 2:
> >>
> https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#
> >> 3: https://github.com/apache/pulsar/issues/11766
> >> 4:
> >>
> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
> >>
> >>
> >> <
> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
> >
> >> Redesign Information Architecture
> >> <
> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
> >
> >> This page was last updated on 2021/11/4 by Anonymitaet.
> >>  Landing page
> Changes
> >> Content blocks On the landing page, categorize tons of info to several
> >> blocks, which allows users to locate desired info quickly. Pulsar Good
> >> example Docker doc we...
> >> docs.google.com
> >>
> >> 
> >> [website] website upgrade · Issue #11766 · apache/pulsar · GitHub
> >> 
> >> Preview make preview supported on netlify #11770 New syntax rules Click
> >> here to see details. Action Base framework init website-next base
> project
> >> #11770 Compatibility process implement custom link remark parser match
> >> {@Inject: prefix:nam...
> >> github.com
> >>
> >> 4:
> >>
> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
> >>
> >> <
> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
> >
> >> Redesign Information Architecture
> >> <
> https://docs.google.com/document/d/1O19v1znrNkoahFpsr8puVQ_20jDQfUjC2eRxdFOL91U/edit#
> >
> >> This page was last updated on 2021/11/4 by Anonymitaet.
> >>  Landing page
> Changes
> >> Content blocks On the landing page, categorize tons of info to several
> >> blocks, which allows users to locate desired info quickly. Pulsar Good
> >> example Docker doc we...
> >> docs.google.com
> >>
> >>
> >> <
> https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#
> >
> >> Upgrade Docusaurus
> >> <
> https://docs.google.com/document/d/1IV35SI_F8G8cL-Vuzknc6RTGLK9_edRMpZpnrHvAWNs/edit#
> >
> >> This page was last updated on 2021/11/4 by Anonymitaet.
> >>  During upgrading
> >> Docusaurus Issues to be fixed The follow issues need to be fixed:
> Function
> >> https://pulsar.apache.org/docs/en/next/functions-package/ Invaild REST
> >> API links Resolved i...
> >> docs.google.com
> >>
> >>
> >> --
> >> *From:* Melissa Logan 
> >> *Sent:* Friday, October 22, 2021 22:01
> >> *To:* Dev 
> >> 

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

[丛搏]

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-154] Max active transaction limitation for transaction coordinator

[Ran Gao]

I think this is a valuable improvement, it could make the Pulsar transaction 
more stable, great work.

+1

best,
Ran Gao

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-154] Max active transaction limitation for transaction coordinator

[PengHui Li]

+1

Penghui

On Sun, Apr 24, 2022 at 10:07 AM Ran Gao  wrote:

> I think this is a valuable improvement, it could make the Pulsar
> transaction more stable, great work.
>
> +1
>
> best,
> Ran Gao
>
> 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-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-152] Support subscription level dispatch rate limiter setting.

[Hang Chen]

+1 (binding)

Thanks,
Hang

Lin Lin  于2022年4月23日周六 21:52写道：
>
> +1
>
> Lin Lin
>
> On 2022/04/19 03:27:39 Haiting Jiang wrote:
> > Hi Pulsar community,
> >
> > This is the voting thread for PIP-152. It will stay open for at least 48 
> > hours.
> >
> > The proposal can be found: https://github.com/apache/pulsar/issues/15094
> >
> > Discuss thread: 
> > https://lists.apache.org/thread/r6dzr09lc42yh79vt0dvmvlv6wtz2czn
> >
> > Thanks,
> > Haiting Jiang
> >

Re: [VOTE] [PIP-152] Support subscription level dispatch rate limiter setting.

[Enrico Olivelli]

+1

Enrico

Il Dom 24 Apr 2022, 06:09 Hang Chen  ha scritto:

> +1 (binding)
>
> Thanks,
> Hang
>
> Lin Lin  于2022年4月23日周六 21:52写道：
> >
> > +1
> >
> > Lin Lin
> >
> > On 2022/04/19 03:27:39 Haiting Jiang wrote:
> > > Hi Pulsar community,
> > >
> > > This is the voting thread for PIP-152. It will stay open for at least
> 48 hours.
> > >
> > > The proposal can be found:
> https://github.com/apache/pulsar/issues/15094
> > >
> > > Discuss thread:
> https://lists.apache.org/thread/r6dzr09lc42yh79vt0dvmvlv6wtz2czn
> > >
> > > Thanks,
> > > Haiting Jiang
> > >
>

Re: [VOTE] [PIP-152] Support subscription level dispatch rate limiter setting.

[Haiting Jiang]

Thanks for your participation.
Close the vote with 4 (+1) bindings and 3 (+1) non-bindings.

Thanks,
Haiting

On 2022/04/24 05:05:46 Enrico Olivelli wrote:
> +1
> 
> Enrico
> 
> Il Dom 24 Apr 2022, 06:09 Hang Chen  ha scritto:
> 
> > +1 (binding)
> >
> > Thanks,
> > Hang
> >
> > Lin Lin  于2022年4月23日周六 21:52写道：
> > >
> > > +1
> > >
> > > Lin Lin
> > >
> > > On 2022/04/19 03:27:39 Haiting Jiang wrote:
> > > > Hi Pulsar community,
> > > >
> > > > This is the voting thread for PIP-152. It will stay open for at least
> > 48 hours.
> > > >
> > > > The proposal can be found:
> > https://github.com/apache/pulsar/issues/15094
> > > >
> > > > Discuss thread:
> > https://lists.apache.org/thread/r6dzr09lc42yh79vt0dvmvlv6wtz2czn
> > > >
> > > > Thanks,
> > > > Haiting Jiang
> > > >
> >
> 

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

[Zixuan Liu]

Hi Pulsar community,

I open a https://github.com/apache/pulsar/issues/15289 for Split client TLS
transport encryption from authentication.

Let me know what you think.

Thanks,
Zixuan

--

Motivation

The client supports TLS transport encryption and TLS authentication, this
code so like:

PulsarClient client = PulsarClient.builder()
.serviceUrl("pulsar+ssl://localhost:6651")
.tlsTrustCertsFilePath("/path/to/cacert.pem")
.authentication(AuthenticationTls.class.getName(), authParams)
.build()

This causes an issue that cannot use other authentication with TLS
transport encryption, and also made our confusion if we use TLS transport
encryption by setting authentication.
Goal

Split client TLS transport encryption from authentication is used to
support TLS transport encryption with any authentication.
API Changes

   - Add new methods in org.apache.pulsar.client.api.ClientBuilder

public interface ClientBuilder extends Serializable, Cloneable {
/** * Set the path to the TLS key file. * * @param
tlsKeyFilePath * @return the client builder instance */
ClientBuilder tlsKeyFilePath(String tlsKeyFilePath);

/** * Set the path to the TLS certificate file. * *
@param tlsCertificateFilePath * @return the client builder
instance */
ClientBuilder tlsCertificateFilePath(String tlsCertificateFilePath);
}

ImplementationTLS transport encryption

We can call the tlsKeyFilePath(), tlsCertificateFilePath() and
tlsTrustCertsFilePath() to configurate the TLS transport encryption, the
code so like:

PulsarClient client = PulsarClient.builder()
.serviceUrl("pulsar+ssl://my-host:6650")
.tlsTrustCertsFilePath("/path/to/cacert.pem")
.tlsKeyFilePath("/path/to/client-key.pem")
.tlsCertificateFilePath("/path/to/client-cert.pem")
.build();

TLS transport encryption with any authentication

We can call the tlsKeyFilePath(), tlsCertificateFilePath(),
tlsTrustCertsFilePath() and authentication() to configurate the TLS
transport encryption with any authentication, the code so like:

PulsarClient client = PulsarClient.builder()
.serviceUrl("pulsar+ssl://my-host:6650")
.tlsTrustCertsFilePath("/path/to/cacert.pem")
.tlsKeyFilePath("/path/to/client-key.pem")
.tlsCertificateFilePath("/path/to/client-cert.pem")
.authentication(AuthenticationTls.class.getName() /*
AuthenticationToken.class.getName()*/, authParams)
.builder()

For AuthenticationTls, we need to do check the authParams, when the
authParams is empty, we need to read TLS config from ClientBuilder,
otherwise read from the authParams
Compatibility

None.