RE: Re: Introducer Pulsar admin api to pulsar-client-go

Hi Zhangjian, I am a PM from StreamNative and we also had some internal discussions related to this topic. Let me share our ongoing planning: * As Penghui mentioned, we will extract the pulsar admin pkg from the pulsarctl to a separate open repo which will be called pulsar-admin-go under

Re: [VOTE] Pulsar Client Python Release 3.1.0 Candidate 3

Hi Zike, I've fixed this crash and showed some explanations in https://github.com/apache/pulsar-client-python/pull/99. PTAL. After it's cherry-picked to branch-3.1, I will open the candidate 4. Thanks, Yunze On Wed, Mar 1, 2023 at 2:57 PM Yunze Xu wrote: > > Hi Zike, > > I've reproduced this

Re: [DISCUSS] Release Pulsar Go Client 0.10.0

Hi, Baodi, Yunze Thanks. Sure, I will wait for them. BR, Zike Yang On Wed, Mar 1, 2023 at 9:02 PM Yunze Xu wrote: > > Please wait for a performance fix for the case when batch index ACK is > enabled, I'm working on it. Currently, the throughput cannot exceed > even 20MB/s when it's enabled. >

Re: [DISCUSS] PIP-246: Improved PROTOBUF_NATIVE schema compatibility checks without using avro-protobuf

Hello Enrico. Thanks for your suggestion, according to my understanding of what you said "flag". How about we add a configuration in the next release: protoBufNativeSchemaValidatorClassName=org.apache.pulsar.broker.service.schema.validator.ProtobufNativeSchemaBreakValidatorImpl Use the previous

[VOTE] Apache Pulsar Adapters Release 2.11.0 Candidate 1

This is the first release candidate for Apache Pulsar Adapters, version 2.11.0. It fixes the following issues: https://github.com/apache/pulsar-adapters/milestone/4?closed=1 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

BC and BC-FIPS differences are the cipher suites. This is similar to TLS1.1 vs 1.2 vs 1.3. Some suites are deprecated (not secured enough due to compute power improvement). in TLS 1.3, client has no chance to specific weak cipher suites to connect to server and exploit the weakness. For BC-FIPS

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

> Actually I was expecting that part of the discussion will specify the > difference between using FIPS compared with non-FIPS, in each BouncyCastle > usage: TLS and message encryption. Good catch! I'll check this. Asaf Mesika 于2023年3月1日周三 21:19写道： > On Mon, Feb 27, 2023 at 4:35 PM Zixuan Liu

Re: [Discuss] PIP-248: Add backlog eviction metric

> > Pulsar has 2 configurations for the backlog eviction > > : backlogQuotaDefaultLimitBytes and backlogQuotaDefaultLimitSecond. > By default, backlog eviction is disabled, and also, there is a field named >

Re: [DISCUSS] PIP-246: Improved PROTOBUF_NATIVE schema compatibility checks without using avro-protobuf

> > Can you please explain how a Protobuf Schema descriptor can be validated > for backward compatibility check using Avro based compatibility rules? > Doesn't it expect the schema to be Avro, but it is actually a Protobuf > descriptor? > Is there some translation happening? 1. *You can take a

Re: [DISCUSS] Change PIP template

+1 Asaf I'd also suggest that we encourage the submission of relevant diagrams. This is trivial to do with the GitHub markdown editor, but I suspect is often neglected because users do not know the feature exists. On Wed, 1 Mar 2023 at 13:22, Asaf Mesika wrote: > Ok. > > I'll draft a PR and

Re: [DISCUSS] Change PIP template

Ok. I'll draft a PR and link it here when I'm done. Thanks! On Tue, Feb 28, 2023 at 7:08 AM PengHui Li wrote: > +1 > > Penghui > > On Mon, Feb 27, 2023 at 9:24 PM Asaf Mesika wrote: > > > Mails don't support things like markdown diagrams or images and are > > generally less easy to read. > >

Re: [DISCUSS] Support processingGuarantees "EFFECTIVELY_ONCE" in python function

Perfect Thanks Enrico Il giorno mer 1 mar 2023 alle ore 04:17 Rui Fu ha scritto: > > +1 > > Best, > > Rui Fu > On Feb 28, 2023 at 05:35 +0800, laminar , wrote: > > Hi all, > > > > I would like to discuss supporting the processingGuarantess > > `EFFECTIVELY_ONCE` in python function runtime. > >

Re: [DISCUSS] Using bouncycastle fips instead bouncycastle non-fips

On Mon, Feb 27, 2023 at 4:35 PM Zixuan Liu wrote: > > users might get exceptions if they don't use specific algorithms or > encryption schemes? > > Could you share more info about this? > Actually I was expecting that part of the discussion will specify the difference between using FIPS

Re: [DISCUSS] PIP-246: Improved PROTOBUF_NATIVE schema compatibility checks without using avro-protobuf

On Mon, Feb 27, 2023 at 3:47 PM SiNan Liu wrote: > > > > I read it and they look identical. What's the difference between them? > > Current avro,json, and protobuf schemas are all implemented based on AVRO. > > What do you mean, they are all implemented based on Avro? You mean the > > protobuf

Re: [DISCUSS] Release Pulsar Go Client 0.10.0

Please wait for a performance fix for the case when batch index ACK is enabled, I'm working on it. Currently, the throughput cannot exceed even 20MB/s when it's enabled. Thanks, Yunze On Wed, Mar 1, 2023 at 8:39 PM Baodi Shi wrote: > > Hi, zike. > > The current pulsar-client-go master branch

Re: [DISCUSS] Release Pulsar Go Client 0.10.0

Hi, zike. The current pulsar-client-go master branch has some flay-test. There may be some internal bugs, I think we need to wait for them to be fixed. - https://github.com/apache/pulsar-client-go/issues/971 Thanks, Baodi Shi 在 2023年3月1日 20:26:10 上，Zike Yang 写道： > I will include this PR

Re: [DISCUSS] Release Pulsar Go Client 0.10.0

I will include this PR https://github.com/apache/pulsar-client-go/pull/968 to this release since it's an important performance improvement. BR, Zike Yang On Wed, Mar 1, 2023 at 8:25 PM Zike Yang wrote: > > Hi everyone, > > I would like to propose releasing the Pulsar Go Client 0.10.0. > > It

[DISCUSS] Release Pulsar Go Client 0.10.0

Hi everyone, I would like to propose releasing the Pulsar Go Client 0.10.0. It has been several months since the last release. And there are several new features and bug fixes in the master branch[0]. It’s time to release a new version. Please let me know if you have any PRs that need to be

Re: [DISCUSS] Release Pulsar 2.10.4

Hello, Pulsar community: The cherry-pick of 2.10.4 is primarily completed. Contains 92 PRs [0]. If you have some PRs that must be included in release-2.10.4, you can reply to me in the email. I will wait for these PRs to be completed before releasing 2.10.4. If you have a PR that urgently needs

[DISCUSS] PIP-252: Configurable compact topic retention

https://github.com/apache/pulsar/issues/19665 -- Elliot West Senior Platform Engineer elliot.w...@streamnative.io streamnative.io

Re: [DISCUSS] Why not split `memoryLimit` into `consumerMemoryLimit ` and `producerMemoryLimit `

Producers and Consumers share many things including memory limit. In some strong cases, maybe use two pulsar clients, one for producer and other for consumer, might be a good choice. Thanks ZhangJian He On Wed, 1 Mar 2023 at 17:15, Zike Yang wrote: > Hi, JIaqi > > Thanks for initiating this

Re: [DISCUSS] Why not split `memoryLimit` into `consumerMemoryLimit ` and `producerMemoryLimit `

Hi, JIaqi Thanks for initiating this discussion. Do you have any cases that need separate limit control for producers/consumers? We have max pending queue size and max message size for the producer, and receiver queue size for the consumer. Although they hardly control the limit as the

[GitHub] [pulsar-adapters] tisonkun merged pull request #41: Only send notifications to commits@ mailing list

tisonkun merged PR #41: URL: https://github.com/apache/pulsar-adapters/pull/41 -- 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-adapters] tisonkun commented on pull request #40: Update to Pulsar 2.11.0

tisonkun commented on PR #40: URL: https://github.com/apache/pulsar-adapters/pull/40#issuecomment-1449628442 > That's weird. It compiles fine on my machine... The Spark version used is very old and there could be an incompatibility with JDK17 @cbornet May I ask how this issue

[GitHub] [pulsar-adapters] RobertIndie opened a new pull request, #41: Only send notifications to commits@ mailing list

RobertIndie opened a new pull request, #41: URL: https://github.com/apache/pulsar-adapters/pull/41 ### Motivation See https://github.com/apache/pulsar-client-cpp/pull/42 and https://github.com/apache/pulsar-client-go/pull/861, The goal is to decrease unnecessary

[GitHub] [pulsar-adapters] cbornet merged pull request #36: [pulsar-kafka] Fixed blockIfQueueFull config

cbornet merged PR #36: URL: https://github.com/apache/pulsar-adapters/pull/36 -- 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-adapters] cbornet merged pull request #37: [improve] Kafka adaptor - Handle partition topic.

cbornet merged PR #37: URL: https://github.com/apache/pulsar-adapters/pull/37 -- 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-adapters] cbornet merged pull request #39: enable Reproducible Builds

cbornet merged PR #39: URL: https://github.com/apache/pulsar-adapters/pull/39 -- 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-adapters] eolivelli merged pull request #40: Update to Pulsar 2.11.0

eolivelli merged PR #40: URL: https://github.com/apache/pulsar-adapters/pull/40 -- 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: