[VOTE] Pulsar Manager Release 0.3.0 Candidate 2

[Li Li]

Hi everyone,
Please review and vote on the release candidate #2 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-2" [4] with git sha 
1449a9dd25f4e7f4f8b9a94136e1b1967b6a95183adc46f4ebef69b489a2e4df4cf5776f51b944150d695ada3f8a5022f8c2fc535873be3512e5ec375a3deb17
  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 


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-src.tar.gz
 


SHA-512 checksums:

51386c4ada76d1ae9916d066e86c7b2a878d9d8e4eeaf9fc35f97ac50c8cb706d014aadd96c60357d9a0fe32580b80e8c5bca2387e02d0029214d62322ad547d
  apache-pulsar-manager-0.3.0-bin.tar.gz
1449a9dd25f4e7f4f8b9a94136e1b1967b6a95183adc46f4ebef69b489a2e4df4cf5776f51b944150d695ada3f8a5022f8c2fc535873be3512e5ec375a3deb17
  apache-pulsar-manager-0.3.0-src.tar.gz

[GitHub] [pulsar-manager] urfreespace opened a new pull request, #458: feat:upgrade version to 0.3.0

[GitBox]

urfreespace opened a new pull request, #458:
URL: https://github.com/apache/pulsar-manager/pull/458

   Signed-off-by: Li Li 
   
   
   *(If this PR fixes a github issue, please add `Fixes #`.)*
   
   feat:upgrade version to 0.3.0
   
   *(or if this PR is one task of a github issue, please add `Master Issue: 
#` to link to the master issue.)*
   
   Master Issue: #
   
   ### Motivation
   
   
   *Explain here the context, and why you're making that change. What is the 
problem you're trying to solve.*
   
   ### Modifications
   
   *Describe the modifications you've done.*
   
   ### Verifying this change
   
   - [ ] Make sure that the change passes the `./gradlew build` checks.
   
   
   


-- 
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: [Discuss] Generate cert and key files automatically

[Zixuan Liu]

You are right, we need to spilt this point.

Yunze Xu  于2022年4月18日周一 15:17写道：

> I have another concern that since we have to use `AuthenticationTls` for
> TLS
> transport encryption, how can we perform a non-TLS authentication? It looks
> like there’s no way to do that.
>
> Thanks,
> Yunze
>
>
>
>
> > 2022年3月23日 11:24，Zixuan Liu  写道：
> >
> >> I think the priority of `AuthenticationTls` must be higher. Then it
> > should be encouraged to use `AuthenticationTls` when TLS authentication
> is
> > enabled at broker side. Otherwise, these two options should be encouraged
> > to use.
> >
> > You are right, if we are set up the `AuthenticationTls` and TLS
> transport,
> > we should use the `AuthenticationTls` data to set up, `AuthenticationTls`
> > must be higher. When the user set up two config, we need to throw an
> > expectation that only use the `AuthenticationTls`, or `tlsCertFilePath`
> and
> > `tlsKeyFilePath`.
> >
> >
> > Yunze Xu  于2022年3月23日周三 01:57写道：
> >
> >> If `tlsCertFilePath` and `tlsKeyFilePath` were added to the client
> builder
> >> options, I think they can also be used for TLS authentication as well.
> >>
> >> I prefer this solution now just because it looks like generating
> >> certificats
> >> automatically is not good, from what Enrico said.
> >>
> >> The problem is that what if we configured both `AuthenticationTls` and
> >> those
> >> two options? Because the underlying mechanisms are the same that a
> >> `SslContext`
> >> is created from the cert and key files and then the `SslContext` object
> >> will be
> >> used in the TCP or HTTP transport.
> >>
> >> I think the priority of `AuthenticationTls` must be higher. Then it
> should
> >> be
> >> encouraged to use `AuthenticationTls` when TLS authentication is
> enabled at
> >> broker side. Otherwise, these two options should be encouraged to use.
> >>
> >> Thanks,
> >> Yunze
> >>
> >>
> >>
> >>
> >>> 2022年3月22日 上午11:03，Zixuan Liu  写道：
> >>>
> >>> Hi Yunze,
> >>>
> >>> The current implementation is confusing, we should split the transport
> >> and
> >>> auth for TLS.
> >>>
> >>> For transport, the code can be so like:
> >>> ```
> >>> PulsarClient client = PulsarClient.builder()
> >>>   .enableTls(true)
> >>>   .tlsTrustCertsFilePath("ca.pem")
> >>>   .tlsCertFilePath("client-ca.pem")
> >>>   .tlsKeyFilePath("client-key.pem")
> >>>   .build();
> >>> ```
> >>>
> >>> For auth, the code can be so like:
> >>> ```
> >>> Map authParams = new HashMap<>();
> >>> authParams.put("tlsCertFile", "client-ca.pem");
> >>> authParams.put("tlsKeyFile", "client-key.pem");
> >>> PulsarClient client = PulsarClient.builder()
> >>>   .enableTls(true)
> >>>   .tlsTrustCertsFilePath("ca.pem")
> >>>   .authentication(AuthenticationTls.class.getName(),
> >>> authParams)
> >>>   .build();
> >>> ```
> >>>
> >>> When using the TLS auth, we don't need to set
> >>> tlsCertFilePath("client-ca.pem") and tlsKeyFilePath("client-key.pem"),
> >> the
> >>> authentication instead of this.
> >>>
> >>> There have an important thing that if we are using the authentication
> >> with
> >>> the token, we cannot setup the TLS transport.
> >>>
> >>>
> >>> Enrico Olivelli  于2022年3月22日周二 00:40写道：
> >>>
>  Il giorno lun 21 mar 2022 alle ore 16:31 Yunze Xu
>   ha scritto:
> >
> > Hi all,
> >
> > Recently I found a document error when configuring Pulsar client for
> >> TLS
> > encryption. See https://github.com/apache/pulsar/issues/14762.
> >> However,
>  the code
> > example in the official documents is more intuitive.
> >
> > See
>  https://pulsar.apache.org/docs/en/security-tls-transport/#java-client
> ,
> >> the
> > example code doesn't configure `AuthenticationTls`, but it is
> required
>  once TLS
> > encryption is enabled, even if TLS authentication is not enabled.
>  Because the
> > client side can only send a SSL handshake via `AuthenticationTls`. It
>  would be
> > confused.
> >
> > Since the cert file and the key file are generated using a CA, whose
>  path is
> > specified by `tlsTrustCertsFilePath` method, I think it would be
>  possible to
> > generate a cert and a key file automatically. We only need to
> specify a
>  common
> > name, which represents the role when authentication is enabled.
> 
>  Usually a service cannot generate a "valid" certificate automatically,
>  it MUST be signed by a CA.
> 
>  We may add an option to automatically generate a certificate (and a
>  CA) but that will work only for
>  DEV environments.
> 
>  Enrico
> 
> 
> >
> > My initial design is, when client configures the
> >> `tlsTrustCertsFilePath`:
> > - If no authentication plugin is enabled, generate the cert and key
> >> files
> > automatically using a default common name.
> > - Otherwise, use the cert and key files spec

[ANNOUNCE] Apache Pulsar 2.10.0 released

[PengHui Li]

The Apache Pulsar team is proud to announce Apache Pulsar version 2.10.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, it also provides transaction
feature since 2.8.0, guaranteed exactly-once semantics for producing and
consuming process over topics, automatic cursor management for
subscribers, and cross-datacenter replication.

For Pulsar release details and downloads, visit:

https://pulsar.apache.org/download

Release Notes are at:
https://pulsar.apache.org/release-notes/#2100

We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team

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

[PengHui Li]

+1

Penghui

On Tue, Apr 19, 2022 at 11:38 AM Haiting Jiang 
wrote:

> Hi Bo,
>
> Do we have metrics like "active transaction usage percent" to  set up
> monitor and alert.
> This is necessary since this critical once the limitation is reached.
>
> Thanks,
> Haiting
>
> On 2022/04/12 12:44:36 丛搏 wrote:
> > pipHi Pulsar community,
> >
> > I open a pip to discuss Max active transaction limitation for
> > transaction coordinator.
> > link: https://github.com/apache/pulsar/issues/15133
> >
> >
> > Thanks,
> > Bo
> >
>

[GitHub] [pulsar-site] DaveDuggins opened a new pull request, #52: Updated sidebar label tags

[GitBox]

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

   See code example.


-- 
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-152] Support subscription level dispatch rate limiter setting.

[PengHui Li]

+1

Penghui

On Tue, Apr 19, 2022 at 11:27 AM 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: [DISCUSS] PIP-155: Drop support for Python2

[Michael Marshall]

Thank you for pushing this initiative through, Matteo. I agree that we
should do this. I had started a draft PR about a month ago that would
have helped, but I ran into some issues with the build [0]. I'm
closing the PR now, but feel free to look at it in case it helps make
your work easier.

Can we cherry pick these changes back to the older release branches
(2.8, 2.9, and 2.10)? I don't see any reason to support python 2.7 for
any future releases. Dropping support primarily saves release managers
time when building the many different python clients.

Thanks,
Michael

[0] https://github.com/apache/pulsar/pull/14827

On Mon, Apr 18, 2022 at 12:36 AM Ran Gao  wrote:
>
> +1
>
> Ran Gao
>
> Best
>
> On 2022/04/15 16:06:36 Matteo Merli wrote:
> > https://github.com/apache/pulsar/issues/15185
> >
> > -
> >
> > ## Motivation
> >
> > Python 2.x has been deprecated for many years now and it was
> > officially end-of-lifed 2.5 years ago
> > (https://www.python.org/doc/sunset-python-2/).
> >
> > We have well reached the point by which we need to drop Python 2.7
> > compatibility for Pulsar client and for Pulsar functions.
> >
> > ## Goal
> >
> > Support only Python 3.5+ for Pulsar client and for Pulsar functions.
> >
> > ## API Changes
> >
> > No changes at this time, though Pulsar Python client library will be
> > now free to use Python3 specific syntaxes and libraries.
> >
> > ## Changes
> >
> > 1. Switch the CI build to run Python client lib tests with Python3
> > 2. Switch integration tests to use Python3
> > 3. Stop building and distributing wheel files for Python 2.7
> >
> >
> >
> >
> > --
> > Matteo Merli
> > 
> >

Re: Performance Engineering Track at ApacheCon NA?

[Sijie Guo]

Hi Sharan,

We will make sure we submit a few talks there.

- Sijie

On Wed, Apr 6, 2022 at 8:18 AM Sharan Foga  wrote:

> Hi Sijie (and everyone else that may be interested)
>
> We have great news - the Performance Engineering track has been accepted
> for ApacheCon NA in New Orleans. So next we will be looking to promote and
> encourage people to submit something for the CFP.
>
> If you'd like to submit something then you can find the call for proposals
> (CFP) on the https://apachecon.com/acna2022/ website and please don't
> forget to select 'Performance Engineering' as the talk category.
>
> We are very excited to have this new track available and are hoping that
> we get some interesting submissions.
>
> Thanks
> Sharan
>
> On 2022/03/19 14:24:38 Sharan Foga wrote:
> > Hi Sijie
> >
> > Thanks very much for the response and interest! I will post an update
> about the track as soon as I have one.
> >
> > Thanks
> > Sharan
> >
> > On 2022/03/15 23:59:46 Sijie Guo wrote:
> > > Sharan,
> > >
> > > I think it is a very great idea to have a performance engineering
> track.
> > > Some committers and I are definitely interested in contributing talks
> to
> > > this track.
> > >
> > > - Sijie
> > >
> > > On Fri, Mar 11, 2022 at 4:44 AM sharanf  wrote:
> > >
> > > > Hi All
> > > >
> > > > The call for tracks for ApacheCon NA is open. There is a suggestion
> to
> > > > try and run a Performance Engineering track at ApacheCon. At the end
> of
> > > > the message I have included some details including a definition of
> what
> > > > we mean by it and some reasoning about why it could be good to run.
> We
> > > > have a list of projects that have something to do with performance
> > > > engineering and if you take a look -  you will see that this project
> is
> > > > on the list!
> > > >
> > > > So what I need is some feedback as to whether the community thinks
> that
> > > > this could be an interesting track topic to run at ApacheCon..and
> more
> > > > importantly would the community be willing to submit talks for it or
> > > > attend ApacheCon to see it.
> > > >
> > > > Like I say - this is just an idea at this stage. If the Performance
> > > > Engineering track does get approval to be included at ApacheCon  -
> do we
> > > > have any volunteers willing to help with managing and promoting the
> > > > track on behalf of the project?
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > > -
> > > >
> > > > *Performance Engineering*  is the science and practice of engineering
> > > > software with the required performance and scalability
> characteristics.
> > > > Many Apache projects focus on solving hard Big Data performance and
> > > > scalability challenges, while others provide tools for performance
> > > > engineering - but there are few projects that don’t care about some
> > > > aspect of software performance.
> > > >
> > > > This track will enable Apache projects members to share their
> > > > experiences of performance engineering best practices, tools,
> > > > techniques, and results, from their own communities, with the
> benefits
> > > > of cross-fertilization between projects. Performance Engineering in
> the
> > > > wider open source community is pervasive and includes methods and
> tools
> > > > (including automation and agile approaches) for performance:
> > > > architecting and design, benchmarking, monitoring, tracing, analysis,
> > > > prediction, modeling and simulation, testing and reporting,
> regression
> > > > testing, and source code analysis and instrumentation techniques.
> > > >
> > > > Performance Engineering also has wider applicability to DevOps, the
> > > > operation of cloud platforms by managed service providers (hence some
> > > > overlap with SRE - Site Reliability Engineering), and customer
> > > > application performance and tuning.  This track would therefore be
> > > > applicable to the wider open source community.
> > > >
> > > > *SUPPORTING DETAILS*
> > > >
> > > > *Google Searches*
> > > > Google “Open source performance engineering” has 4,180,000,000
> results
> > > > Google “site:apache.org  performance” has 147,000
> > > > results
> > > >
> > > > *Apache Projects *which may have some interest in, or focus on,
> > > > performance (just the top results):
> > > > JMeter, Cassandra, Storm, Spark, Samza, Pulsar, Kafka, Log4J,
> SystemML,
> > > > Drill, HTTP Server, Cayenne, ActiveMQ, Impala, Geode, Flink, Ignite,
> > > > Impala, Lucene, TVM, Tika, YuniKorn, Solr, Iceberg, Dubbo, Hudi,
> > > > Accumulo, Xerces, MXNet, Zookeeper
> > > >
> > > > *Incubator projects *which may have some interest in, or focus on,
> > > > performance**(again just top results):
> > > > Crail, Eagle, Nemo, Skywalking, MXnet, HAWQ, Mnemonic, CarbonData,
> > > > Drill, ShenYu, Tephra, Sedona
> > > >
> > > > *References *(randomly selected to show the range of open-source
> > > > performance engineering topics available, rather than the quality of
> > > > ar

Pulsar Summit San Francisco 2022 CFP is open!

[Sijie Guo]

Hi, all the Pulsar community members,

Pulsar Summit San Francisco 2022 CFP is open now! It will be our *first-ever
in-person Pulsar Summit *in San Francisco! We're glad to invite you to
share your experience and add up to the wonderfulness.

As a speaker, you will receive the chance to demonstrate your experience
and deep knowledge, and your bio and session featured on the Pulsar Summit
website. We would also like you to help us make Pulsar Summit San Francisco
2022 a big success by spreading the word on Twitter, LinkedIn, and other
social media platforms.

Please submit your talks [1] by May 20th (Pacific Time). We
welcome submissions from around the globe. Also, first-time speakers are
welcomed. For more details, please check the submission link, and do not
hesitate to contact us at organiz...@pulsar-summit.org if you have any
questions.

We look forward to your participation and hope to see you in person in San
Francisco!

For any more updates about Pulsar Summit San Francisco, you can follow
@PulsarSummit  on Twitter or add yourself
to the waitlist on the home page .

[1] Submission link: https://sessionize.com/pulsar-summit-san-francisco-2022
[2] Pulsar Summit Homepage: https://pulsar-summit.org/

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

[Dezhi Liu]

+1

Dezhi Liu

[GitHub] [pulsar-site] urfreespace merged pull request #53: changes from user feedback

[GitBox]

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


-- 
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-152] Support subscription level dispatch rate limiter setting.

[Zike Yang]

+1

Thanks,
Zike

On Wed, Apr 20, 2022 at 9:20 AM Dezhi Liu
 wrote:
>
> +1
>
> Dezhi Liu

Re: Categorize Pulsar Plugins

[Yu]

Hi Chris,

Thank you very much for providing useful information! I've added them all
to the sheet.

For categories, I have two quick questions:

#1. For Starlight for JMS [1]
I see you categorize it as "Client API". Does it make sense to categorize
it as "Client Wrapper"? (which is the same as the Kafka Client Wrapper [2])

#2. For OpenID Connect Authentication Plugin [3]
I see you categorize it as "Authentication Plugin". Does it make sense to
categorize it as "Security Plugin"? It is more general and "extendable"
since we can include more security-related plugins (eg.
authentication/authorization plugins) in the future.

Let me know what you think, thanks!

[1] https://github.com/datastax/pulsar-jms
[2]
https://github.com/apache/pulsar-adapters/tree/master/pulsar-client-kafka-compat
[3] https://github.com/datastax/pulsar-openid-connect-plugin

Anonymitaet

On Wed, Apr 20, 2022 at 2:08 AM Chris Bartholomew <
chris.bartholo...@kesque.com> wrote:

> Hi Anonymitaet,
>
> I provided input on the  "Components Managed by DataStax" as a comment in
> the Google doc. If you need any more information, please let me know.
>
> Cheers,
> Chris
>
>
> On Mon, 18 Apr 2022 at 06:36, Yu  wrote:
>
>> Hi Pulsarers,
>>
>>
>> For the Ecosystem Page [1], we want to make it a place for the Pulsar
>> community to come together and share the components the community needs to
>> build better streaming data pipelines and event-driven applications.
>>
>>
>> So I've collected all Pulsar-related plugins and tried to re-categorize
>> them **based on scenarios**.
>>
>>
>> For the "Components Managed by DataStax", does anyone can help review the
>> "Category"? [2] We're unsure about it.
>>
>>
>> Feel free to review the whole sheet and comment if I miss or
>> misunderstand anything, thank you!
>>
>>
>> [1] https://pulsar-next.staged.apache.org/ecosystem/
>>
>> [2]
>> https://docs.google.com/spreadsheets/d/1n4oAQx_hxBaEYkHiVVRVTVpOKfE26i4am6UYieriXYQ/edit#gid=0
>>
>>
>> Anonymitaet
>>
>>
>>

[GitHub] [pulsar-dotpulsar] kandersen82 opened a new pull request, #102: Fix performance issue with ReadUint32

[GitBox]

kandersen82 opened a new pull request, #102:
URL: https://github.com/apache/pulsar-dotpulsar/pull/102

   The loop would not correctly break after reading 4 bytes.


-- 
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