Re: [DISCUSS] PIP-324: Alpine Docker images

Le mer. 13 déc. 2023 à 18:03, Matteo Merli a écrit : > > -- > Matteo Merli > > > > On Wed, Dec 13, 2023 at 8:20 AM Christophe Bornet > wrote: > > > Thanks Matteo for bringing this subject. > > > > I share the concerns of Lari regarding the mov

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.1 Candidate 1

+0 The git commit is incorrect in the voting mail (d45c08827387bd8d2a0d6bdc542c2bf7e4ebcda8 instead of 92a1e390e854876b54936bd0e6d21bf1e5071aeb) I don't think it needs a new RC but I believe it needs a new voting mail with the correct commit. Regards Christophe Le mer. 13 déc. 2023 à 22:59,

Re: [DISCUSS] PIP-324: Alpine Docker images

Thanks Matteo for bringing this subject. I share the concerns of Lari regarding the move from glibc to musl in terms of security, performance, compatibility with the JVM. Extensive performance tests will have to be done. Also, last time I tried to use alpine with a Python project, it was a

Re: [VOTE] Reactive Java client for Apache Pulsar 0.5.0 Candidate 2

ce package and promote the maven packages to be synchronized to maven central. Christophe Bornet Le ven. 17 nov. 2023 à 23:06, Zili Chen a écrit : > > +1 binding > > - Checksum and signature matches. > - LICENSE and NOTICE are good. > - `gradle build` passed with JDK 17. >

[VOTE] Reactive Java client for Apache Pulsar 0.5.0 Candidate 2

package, and follow detailed instructions for pulsar-client-reactive release validation at https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation . Best regards Christophe Bornet

Re: Question about Pulsar gRPC client(s)

(simpler to deal with, usable with simple CLI tools, browsers, etc...). So I'm pretty sure we need at least an HTTP+JSON interface. As you say, it could be brought by the gRPC gateway but that's an additional component to deploy and it cannot be embedded in the broker as it's written in Go. > Best,

Re: Question about Pulsar gRPC client(s)

Hi Kiryl, Thanks for mentioning pulsar-grpc. Indeed, using gRPC simplifies the implementation of the networking logic (keep-alive, reconnection, flow control,…). On the other hand, the Java gRPC implementation makes a lot of buffer copies to cleanly separate the network and app layers but that

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

Nice. Would it be possible to have a daily build on JDK 21 to ensure it runs properly ? Le ven. 20 oct. 2023 à 00:34, Lari Hotari a écrit : > > Hi all, > > I can now confirm that apache/pulsar master branch compiles and runs all > tests in Pulsar CI successfully with Java 21. Therefore, we have

Re: [DISCUSS] Moving to Java 21 for development and Pulsar server component runtime

+1. It's important to support the latest JDK LTS. Le mer. 18 oct. 2023 à 00:02, Lari Hotari a écrit : > > Dear Pulsar community, > > Java 21 was released on September 19th and has now become the current Java > LTS release. > > I've begun preparations in the Pulsar code base to allow for Java 21

[ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.4.0

The Apache Pulsar team is proud to announce the Reactive client for Apache Pulsar, version 0.4.0. The Reactive client for Apache Pulsar can be used together with any Reactive Streams implementation on the JVM. Examples include Project Reactor / Spring Reactive, Akka Streams, RxJava 3, Vert.x,

Re: [VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1

ce package and promote the maven packages to be synchronized to maven central. Christophe Bornet Le lun. 9 oct. 2023 à 05:12, Nicolò Boschi a écrit : > +1 binding > > I followed the instructions from here - > https://github.com/apache/pulsar-client-reactive > /wiki/Release-p

[VOTE] Reactive Java client for Apache Pulsar 0.4.0 Candidate 1

package, and follow detailed instructions for pulsar-client-reactive release validation at https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation . Best regards Christophe Bornet

Re: [DISCUSS] Release Pulsar 3.0.1

+1 Le lun. 5 juin 2023 à 03:44, Zixuan Liu a écrit : > +1 > > Thanks, > Zixuan > > Hang Chen 于2023年6月5日周一 09:39写道： > > > > +1 > > > > Thanks, > > Hang > > > > PengHui Li 于2023年6月5日周一 09:34写道： > > > > > > +1 > > > > > > Thanks for driving the release. > > > > > > Penghui > > > > > > On Thu,

Re: [VOTE] Pulsar Release 3.0.0 Candidate 4

+1 (non-binding) - Verify sigs - Test functions and connectors with bin - Test Starlight-for-RabbitMQ and Pulsar-transformations with ARM64 docker image Christophe Le jeu. 27 avr. 2023 à 13:47, Christophe Bornet a écrit : > This is the fourth release candidate for Apache Pulsar, version 3.

[VOTE] Pulsar Release 3.0.0 Candidate 4

. Thanks Christophe Bornet

Re: [VOTE] Pulsar Release 3.0.0 Candidate 3

r 27, 2023 at 12:27 AM Matteo Merli wrote: > > > > +1 > > > > Checked signatures, standalone & docker images. > > > > > > -- > > Matteo Merli > > > > > > > > On Tue, Apr 25, 2023 at 7:38 AM Christophe Bornet > >

[ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.3.0

The Apache Pulsar team is proud to announce the Reactive client for Apache Pulsar, version 0.3.0. The Reactive client for Apache Pulsar can be used together with any Reactive Streams implementation on the JVM. Examples include Project Reactor / Spring Reactive, Akka Streams, RxJava 3, Vert.x,

Re: [VOTE] Reactive Java client for Apache Pulsar 0.3.0 Candidate 1

ce package and promote the maven packages to be synchronized to maven central. Christophe Bornet Le mer. 26 avr. 2023 à 11:22, Nicolò Boschi a écrit : > > +1 binding > - verified signatures and checksum > - ran all tests from src artifact with jdk17 and gradle 8 > > Nicolò Bosch

[VOTE] Pulsar Release 3.0.0 Candidate 3

. Thanks Christophe Bornet

Re: [NOTICE] Please don't cherry-pick commits to branch-3.0 without consensus

> > features? > > > > > I 100% agree > But RM but be aware and they should do the cherry picks > > Enrico > > > > Or the testing should be completed before the code freeze, otherwise, push > > to the next feature release. > > > > Thanks, > > Peng

Re: [NOTICE] Please don't cherry-pick commits to branch-3.0 without consensus

ry-pick on the mailing list. > > > > For the LTS release, we need to be very careful when cherry-picking > > > > the commit. All cherry-picked commits that enter the LTS version > > > > should be noticed for everyone. They should all be considered as > > > > important cha

Re: [NOTICE] Please don't cherry-pick commits to branch-3.0 without consensus

So to respect the code freeze, I propose to revert all those commits except: https://github.com/apache/pulsar/pull/19849 https://github.com/apache/pulsar/pull/20086 I understand that the optimization PRs are nice but if we start to accept them, why not accepting all the others and the code freeze

Re: [NOTICE] Please don't cherry-pick commits to branch-3.0 without consensus

This process is already documented : https://pulsar.apache.org/contribute/release-policy/#release-cycles "For feature releases and LTS releases, the last 3 weeks of the release cycle will be marked as a code-freeze period. The RM will branch off from master, and the RM is also responsible for

[VOTE] Reactive Java client for Apache Pulsar 0.3.0 Candidate 1

package, and follow detailed instructions for pulsar-client-reactive release validation at https://github.com/apache/pulsar-client-reactive/wiki/Release-process#release-validation . Best regards Christophe Bornet

Re: [DISCUSS] forbid user to upload `BYTES` schema

> > 1. If yes, warn the user that it is not necessary to upload bytes > > > > schema. > > > > You can subscribe to a topic using bytes schema. > > > > 2. If there is no schema, warn the user that the topic does not have a > > > > schema. The de

Re: [DISCUSS] Dropping the StreamingDispatcher

Shouldn't it first be deprecated before removal ? Le mar. 4 avr. 2023 à 08:47, Enrico Olivelli a écrit : > > Hello, > It has been a long time that we have in the Pulsar code a new > experimental Dispatcher implementation named StreamingDispatcher. > > https://github.com/apache/pulsar/pull/9056 >

Re: [Discuss] Add a phase to process pending PRs before code freeze

Hi Yunze, Thanks for bringing this discussion. I agree that there must be some step to remind everybody that a code freeze is coming and that people should pay attention to their open PRs if they want them included. In a sense Zike's mail one week ago did this and was pretty clear on what was

Re: [DISCUSS] We must change the way we review PIPs

Big +1 for me Le jeu. 30 mars 2023 à 22:27, Asaf Mesika a écrit : > > Hi all, > > In the last 2 months, I've increased my PIP review time (I do it in > cycles), and reviewed quite a few PIPs. > > My conclusion as a result of that: > > It's nearly impossible to review PIPs using a mailing list. >

Re: [DISCUSS] forbid user to upload `BYTES` schema

This change broke the Flink SQL Pulsar connector: https://github.com/streamnative/flink/issues/270 So I propose to revert it. Le ven. 9 déc. 2022 à 11:57, labuladong a écrit : > > Hi pulsar community, > > > I'd like to discuss the behavior of schema uploading, for more context see >

[ANNOUNCE] Apache Pulsar Adapters 2.11.0 released

The Apache Pulsar team is proud to announce Apache Pulsar Adapters version 2.11.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, automatic cursor

Re: [VOTE] Apache Pulsar Adapters Release 2.11.0 Candidate 3

; > > Il giorno mar 7 mar 2023 alle ore 09:57 Enrico Olivelli > > > > ha scritto: > > > > > Nice work Christophe, thanks for driving this release > > > > > > +1 (binding) > > > > > > - verified checksums/signatures > > >

[VOTE] Apache Pulsar Adapters Release 2.11.0 Candidate 3

This is the release candidate 3 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

[VOTE] Apache Pulsar Adapters Release 2.11.0 Candidate 2

This is the release candidate 2 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

[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: [ANNOUNCE] New committer: Yuri Mizushima

Congrats Yuri! Le lun. 27 févr. 2023 à 15:54, 太上玄元道君 a écrit : > congrats! > > Thanks, > Tao Jiuming > > Nozomi Kurihara 于2023年2月27日周一 15:47写道： > > > Hi everyone, > > > > The Project Management Committee (PMC) for Apache Pulsar > > has invited Yuri Mizushima (https://github.com/equanz) to

[DISCUSS] Apache Pulsar Adapters 2.11.0 release

release. I'll also update the dependency on Pulsar to use 2.11. Please tell if you have things you want to do, issues you want to see fixed or PRs you'd like to see merged before this release. Best regards. Christophe Bornet

Re: [PROPOSAL] Roadmap for 3.0 release

+1 Also, I'd like to volunteer as a release manager for this release. Christophe Le ven. 17 févr. 2023 à 23:44, Matteo Merli a écrit : > > Since the LTS release model has been formally approved, I'm proposing > the following schedule for the release: > > * Tue - 2023-05-11 >- RC-1

Re: Force redirect questions from Slack to GitHub Discussions or StackOverflow?

+100 Also note that for good or bad reasons, the number of questions on StaOverflow is often used as a metric for the popularity of a project. Le mer. 15 févr. 2023 à 13:12, Kiryl Valkovich a écrit : > Hi everyone! Enrico Olivelli asked me to repost it to the mailing list. > > --- Me > I’m very

[ANNOUNCE] Released Reactive client for Apache Pulsar, version 0.2.0

The Apache Pulsar team is proud to announce the Reactive client for Apache Pulsar, version 0.2.0. The Reactive client for Apache Pulsar can be used together with any Reactive Streams implementation on the JVM. Examples include Project Reactor / Spring Reactive, Akka Streams, RxJava 3, Vert.x,

Re: [VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 2

co Olivelli > wrote: > > > > > > +1 (binding) > > > - built from sources on jdk11 on Mac M1 > > > - all tests are passing > > > - gradle check passes (it runs RAT) > > > - verified signatures and checksum > > > > > > > >

[VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 2

This is the release candidate 2 for the Reactive Java client for Apache Pulsar, version 0.2.0. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag). Binaries in the Maven repository are provided for

[VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 1 (updated)

New voting thread with links to artifacts signed with an rsa4096 key. Please ignore the previous mails and vote on this one. This is the release candidate 1 for the Reactive Java client for Apache Pulsar, version 0.2.0. *** Please download, test and vote on this release. This vote will stay open

Re: [VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 1

There's a typo in the release tag link so please ignore this mail and vote on the new mail that was sent. Best regards Christophe Le lun. 30 janv. 2023 à 20:00, Christophe Bornet a écrit : > This is the release candidate 1 for the Reactive Java client for Apache > Pulsar, version

[VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 1

This is the release candidate 1 for the Reactive Java client for Apache Pulsar, version 0.2.0. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag). Binaries in the Maven repository are provided for

[VOTE] Reactive Java client for Apache Pulsar 0.2.0 Candidate 1

This is the release candidate 1 for the Reactive Java client for Apache Pulsar, version 0.2.0. *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note that we are voting upon the source (tag). Binaries in the Maven repository are provided for

Re: [VOTE] PIP-236: Record schema in the request and carry to the broker when subscribing with AUTO_CONSUME schema.

+1 (non-binding) Le ven. 20 janv. 2023 à 12:06, SiNan Liu a écrit : > Hello community, > > I'm starting the VOTE for PIP-236: Record schema in the request and carry > to the broker when subscribing with AUTO_CONSUME schema. > > PIP link: > https://github.com/apache/pulsar/issues/19113 > >

Re: [ANNOUNCE] Nicolò Boschi as new PMC member in Apache Pulsar

Congrats, Nicolo ! Le ven. 20 janv. 2023 à 14:27, Enrico Olivelli a écrit : > Congratulations ! > > Enrico > > Il giorno ven 20 gen 2023 alle ore 13:36 Lari Hotari > ha scritto: > > > > Dear Community, > > > > We are thrilled to announce that Nicolò Boschi > > (https://github.com/nicoloboschi)

Re: [DISCUSS] Code freeze for Pulsar 2.12

code has already > >> been added locally and only requires some rebase to resolve conflicts. > >> > >> [1] https://github.com/apache/pulsar/pull/19158 > >> > >> Thanks, > >> Yunze > >> > >>> On Fri, Jan 20, 2023 at 7:46 AM

Re: [DISCUSS] Code freeze for Pulsar 2.12

> > > > 2.11 has just been released and the release cycle is set to 3 months. > The release cycle wasn't really respected for 2.11... We already have 5 months worth of features on the master branch and nothing tells us that the release of 2.12 won't take 5 more months. And if we add 3 months to

[DISCUSS] Code freeze for Pulsar 2.12

Hi Pulsar community, It's great that we released Pulsar 2.11. It has taken quite some time to stabilize the release branch and now we have more than 5 months of awesome features and commits on the master branch that would benefit a lot to our users. That's why I'd like to propose to start a code

Re: [VOTE] PIP-243: Register Jackson Java 8 support modules by default

+1 Le lun. 16 janv. 2023 à 11:16, Lari Hotari a écrit : > Hello community, > > I'm starting the VOTE for PIP-243: Register Jackson Java 8 support modules > by default. > > Motivation: > Jackson has a separate Java 8 support modules for adding support for > proper serialization and

Re: [ANNOUNCE] Yunze Xu as a new PMC member in Apache Pulsar

Congrats Yunze ! Le jeu. 29 déc. 2022 à 13:42, Haiting Jiang a écrit : > Hi all, > > The Apache Pulsar Project Management Committee (PMC) has invited Yunze Xu > (https://github.com/BewareMyPower) as a member of the PMC and we are > pleased to announce that he has accepted. > > He is very active

Re: [ANNOUNCE] Released Spring for Apache Pulsar, version 0.1.0

That's awesome Chris, Many thanks to VMWare and all the contributors. This is a really great addition to the Apache Pulsar eco-system ! Christophe Le mar. 20 déc. 2022 à 18:09, Chris Bo a écrit : > The Spring for Apache Pulsar team is proud to announce the initial GA minor > release of the

Re: [VOTE] Reactive Java client for Apache Pulsar 0.1.0 Candidate 2

+1 (non-binding) - Followed the release validation procedure: - verified checksum and signature - verified sources match git tag - Ran successfully Spring-Pulsar test suite with the staged artifacts from the Maven repo Best regards. Christophe Le jeu. 8 déc. 2022 à 14:31, Lari Hotari

Re: [VOTE] Reactive Java client for Apache Pulsar 0.1.0 Candidate 1, #2 vote

Good points Dave. Thanks for your feedback. Le mer. 7 déc. 2022 à 22:43, Dave Fisher a écrit : > Hi - > > -1 (binding) > > 1. grade-wrapper.jar is a compiled binary and is not allowed. You can > provide a script to be run to download it. See > issues.apache.org/jira/browse/CALCITE-4575 > > 2.

[VOTE] Reactive Java client for Apache Pulsar 0.1.0 Candidate 1

Christophe Bornet (cbornet)

Re: [VOTE] Pulsar Release 2.11.0 Candidate-2

+1 (non-binding) - Start docker image standalone - Test HTTP Sink - Test Transformation Function Best regards Christophe Le lun. 28 nov. 2022 à 13:57, guo jiwei a écrit : > This is the second release candidate for Apache Pulsar, version 2.11.0. > > This release contains 1574 commits by 64

Re: [VOTE] PIP-208: HTTP Sink

at 12:49 PM Niclas Hedhman > wrote: > > > > > > > > > > > +1 non-binding > > > > > > > > Niclas > > > > > > > > On 2022-10-13 19:34, Christophe Bornet wrote: > > > > > Hi fo

Re: [DISCUSS] PIP-208: HTTP Sink

> > I think we could shrink the connectors a lot by removing from the NAR > archives dependencies that are already present in the > pulsar-functions-instance. > I mean java-instance.jar Le mer. 19 oct. 2022 à 12:29, Christophe Bornet a écrit : > The pulsar-all docker imag

Re: [DISCUSS] PIP-208: HTTP Sink

gt; > added to the `pulsar-all` distribution. > > The pulsar-all docker image is pretty big. I assume we will continue > to build and package additional connectors. It would be great to > figure out how to make it smaller at some point. > > Thanks, > Michael > > > On Tue, Sep 2

Re: [DISCUSS] PIP-208: HTTP Sink

est one real-world integration test you can make use of: > https://clickhouse.com/docs/en/integrations/kafka/kafka-connect-http > (replace source kafka with pulsar). > > Best, > tison. > > > Enrico Olivelli 于2022年9月27日周二 18:04写道： > > > Thanks for your answers.

Re: [DISCUSS] Apache Pulsar 2.11.0 Release

The blockers mentioned by Nicolo seem to have been fixed. Is there still something blocking the release ? Le mer. 28 sept. 2022 à 15:36, Nicolò Boschi a écrit : > I've found another release blocker about client compatibility with jdk8/11, > please review

[VOTE] PIP-208: HTTP Sink

Hi folks, I'd like to start a vote for the PIP-208: HTTP Sink ( https://github.com/apache/pulsar/issues/17719) The discussion can be found here: https://lists.apache.org/thread/9brckr22l5s3y072fs946vxhxnzz5km7 Best regards. Christophe

Re: [DISCUSS] PIP-208: HTTP Sink

o demo it with a > prototype HTTP sink or after the patch gets merged :) > > Best, > tison. > > > Christophe Bornet 于2022年9月27日周二 18:51写道： > > > Hi Tison, > > > > Very interesting and shows the value of such a HTTP Sink. > > The Pulsar HTTP Sink should work OOTB w

Re: [DISCUSS] PIP-208: HTTP Sink

Hi Tison, Very interesting and shows the value of such a HTTP Sink. The Pulsar HTTP Sink should work OOTB with ClickHouse. I don't have time to do the test right now, so would someone want to do it ? Best regards. Christophe Bornet Le mar. 27 sept. 2022 à 12:31, tison a écrit : >

Re: [DISCUSS] PIP-208: HTTP Sink

; Yes. Batching could be implemented as a follow-up task. > > Best, > Alex > > On Tue, Sep 20, 2022 at 2:16 PM Enrico Olivelli > wrote: > > > Christophe, > > very good initiative! > > > > I support it > > Some comments inline below > > >

Re: [DISCUSS] PIP-208: HTTP Sink

override the content-type. If we go for a variable content-type depending on the schema, then we could have a map > Can we make the HTTP METHOD configurable ? > Yes we can. But do we do it for the first iteration ? > > > ### Alternatives > > > > Creating a separated project for this Sink is rejected since: > > * this Sink is very useful for developers to test the Pulsar IO > framework, > > transform functions, and to make demos. > > * the code has a very small footprint with no external dependencies. > > * it should be visible at the same level as other sinks > > 100% agreed ! > > > > > I'm looking forward the discussion. > > > > Best regards, > > > > Christophe Bornet >

Re: Announcing first milestone release of Spring for Apache Pulsar

Awesome Soby ! Le mar. 20 sept. 2022 à 18:10, Soby Chacko a écrit : > Hi Apache Pulsar Community, > > We are very happy to announce the first milestone release of Spring for > Apache Pulsar. More details can be found here: > >

[DISCUSS] PIP-208: HTTP Sink

at the same level as other sinks I'm looking forward the discussion. Best regards, Christophe Bornet

Re: [DISCUSS] Call to improve Pulsar contributor's experience

Hi Lari, Thanks for launching this discussion. There's a lot to do to improve contributor experience, esp for newcomers I think. One of the pain points is obviously the CI flakyness and I believe we are all aware of that. Related to that, we have the pulsarbot to relaunch the tests that failed

Re: [VOTE] PIP-205: Reactive Java client for Apache Pulsar

+1 (non-binding) Le mer. 31 août 2022 à 16:06, Lari Hotari a écrit : > Hello, > > This is the official VOTE thread for PIP-205: Reactive Java client for > Apache Pulsar. > PIP link: https://github.com/apache/pulsar/issues/17335 > discussion: >

Re: [DISCUSS] PIP-204: Reactive Java client for Apache Pulsar

+1 Reactive is a perfect fit for streaming platforms. Le lun. 29 août 2022 à 15:11, Lari Hotari a écrit : > I updated it to be PIP-205 since there was a previous reference of > PIP-204. :) > > -Lari > > On 2022/08/29 12:55:43 Lari Hotari wrote: > > Hi all, > > > > I have drafted PIP-204:

Re: [DISCUSS] Move PIPs to the codebase?

+1 from me. (I've always been a supporter of having PIPs in codebase) Le mer. 24 août 2022 à 18:04, Michael Marshall a écrit : > I support moving PIPs to the code base. > > When we discussed this option during last year's redesign of the PIP > process, an objection was that "merging" a PIP

Re: [VOTE] PIP-193 : Sink preprocessing Function

ng) > > > > Good proposal. My only comment is about the naming. Instead of calling > it a "preprocessing function" or "extra function", I'd propose calling it > "decorator function". > > > > -Lari > > > > On 2022/07/28 10:39:35 C

Re: [DISCUSS] Skip unnecessary tests when there are only cpp/python related changes

+1 Le mer. 10 août 2022 à 09:36, Zike Yang a écrit : > Hi, Pulsar community > > Currently, Java tests consume significant CI resources. And it is not > necessary to run all the tests for changes that are only on the C++ or > python parts of the code. I have created a PR [0] to improve the CI by

Re: [DISCUSS] PIP 193 : Sink preprocessing Function

nto allowing users to change a source/sink in the > PulsarFunction pipeline instead of tweaking the Sink? > > Syntax could be: > ``` > pulsar-admins functions create --sink ... --source ... > ``` > > This will be more flexible and opens a lot possibility for further > developme

[VOTE] PIP-193 : Sink preprocessing Function

48 hours. Best regards. Christophe Bornet

Re: [ANNOUNCE] Micheal Marshall as a new PMC member in Pulsar

Congratulations Michael ! Well deserved ! Le mar. 26 juil. 2022 à 17:22, Enrico Olivelli a écrit : > I am glad to announce that the Apache Pulsar PMC invited Micheal to > join the PMC and he accepted. > > Micheal is doing a great job in stewarding our community > > Please join me and celebrate

Re: [DISCUSS] PIP 193 : Sink preprocessing Function

it's already possible > to > > write a Function>. > > And when declaring a Sink with a Function we'll check that it's the case. > > > > I mean: we should constrain the function interface, otherwise, the user > > may return a structure that is not a record. &

Re: [DISCUSS] PIP 193 : Sink preprocessing Function

e, the user > may return a structure that is not a record. > > Thanks, > Baodi Shi > > > On Jul 25, 2022, at 01:0233, Christophe Bornet > wrote: > > > > Thanks for the feedback Asaf > > > > > >>> - preprocess-function: the preprocess f

Re: [DISCUSS] PIP 193 : Sink preprocessing Function

arter directly. The command line is forged by the ProcessRuntime and KubernetesRuntime. > > > In general, you will essentially have two class loaders - one for the sink > and one for the pre-process function? > Yes, exactly. 3 to be more accurate since there's also the instance class loader

Re: [DISCUSS] PIP 193 : Sink preprocessing Function

Thanks, > Baodi Shi > > > On Jul 22, 2022, at 17:4828, Christophe Bornet > wrote: > > > > Dear Pulsar dev community, > > > > I would like to open a discussion here about PIP 193 : Sink preprocessing > > Function <https://github.com/apache/pulsar/issu

[DISCUSS] PIP 193 : Sink preprocessing Function

Dear Pulsar dev community, I would like to open a discussion here about PIP 193 : Sink preprocessing Function . Best regards Christophe ## Motivation Pulsar IO connectors make it possible to connect Pulsar to an external system: * A Source reads

Re: [VOTE] PIP-187 Add API to analyze a subscription backlog and provide a accurate value

+1 Le mar. 19 juil. 2022 à 20:01, Andrey Yegorov a écrit : > +1 > > On Tue, Jul 19, 2022 at 10:51 AM Dave Fisher wrote: > > > +1 (binding) > > > > I support this enhancement for when a user occasionally requires accurate > > backlog stats. Once we bring this into service we can see if further

Re: [VOTE] PIP-181: Pulsar Shell

+1 (non binding) Le lun. 4 juil. 2022 à 16:46, Nicolò Boschi a écrit : > Dear Community, > > I would like to start a VOTE on "PIP-181: Pulsar Shell" > > The proposal can be read at [0] and the discussion thread is available at > [1]. > Voting will stay open for at least 48h. > > [0]

Re: [VOTE] Pulsar Release 2.10.1 Candidate 1

+1 (non-binding) * run docker image * test protocol handlers * test proxy extensions Thanks Christophe Le lun. 13 juin 2022 à 13:43, PengHui Li a écrit : > This is the first release candidate for Apache Pulsar 2.10.1 > > It fixes the following issues: > >

Re: [DISCUSS] PIP-173 : Create a built-in Function implementing the most common basic transformations

nrico Olivelli > wrote: > > > Overall I agree with the proposal. > > I left some minor feedback on the issue > > > > Thank you > > > > Enrico > > > > Il giorno gio 2 giu 2022 alle ore 16:57 Christophe Bornet > > ha scritto: > >

[DISCUSS] PIP-173 : Create a built-in Function implementing the most common basic transformations

Dear Pulsar community, I opened PIP-173 https://github.com/apache/pulsar/issues/15902 to create a built-in Function implementing the most common basic transformations. Let me know what you think. Best regards, Christophe -- ## Motivation Currently, when users want to modify the data in

Re: [VOTE] PIP-168: Support zero-copy of NIC to NIC on Proxy

+1 Le mar. 31 mai 2022 à 10:33, Zixuan Liu a écrit : > +1 (non-binding) > > On 2022/05/26 13:40:30 zhaocong wrote: > > Hi Pulsar Community, > > > > > > I would like to start a VOTE on "Support zero-copy of NIC to NIC on > Proxy" > > (PIP-168). > > > > > > The proposal can be read at >

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

+1 for "Preemptive". Le ven. 27 mai 2022 à 00:22, Neng Lu a écrit : > Hi All, > > Would "Preemptive" Mode make sense? > > On Wed, May 11, 2022 at 8:56 AM Matteo Merli > wrote: > > > +1 > > > > > > On Tue, May 10, 2022 at 5:56 AM Enrico Olivelli > > wrote: > > > > > Hello, > > > I created a

Re: [ANNOUNCE] New Committer: Nicolò Boschi

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

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

+1 Le ven. 15 avr. 2022 à 18:06, Matteo Merli a écrit : > 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/). > >

Re: [ANNOUNCE] Apache Pulsar 2.10.0 released

Great work everyone ! Le mar. 19 avr. 2022 à 11:23, PengHui Li a écrit : > 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,

Re: [DISCUSS] PrometheusMetricsServlet performance improvement

Note that the PrometheusMetricsGenerator will generate the text for Prometheus client metrics registered to the default CollectorRegistry. So it should be possible to progressively convert stats objects to Prometheus Gauge/Counter/etc... Le mer. 9 mars 2022 à 06:57, Michael Marshall a écrit : >

Re: [ANNOUNCE] New Committer: Andrey Yegorov

Congratulations Andrey ! Le lun. 7 mars 2022 à 20:26, Dave Fisher a écrit : > The Apache Pulsar Project Management Committee (PMC) has invited Andrey > Yegorov > https://github.com/dlg99 to become a committer and we are pleased to > announce that he has accepted. > > Andrey has made great

Re: [DISCUSS] PIP 141 : Pulsar BOM

et? Protocol Handlers? Servlets? Proxy extensions? > > > Enrico > > Il Lun 14 Feb 2022, 15:05 Nicolò Boschi ha scritto: > > > Great idea! > > +1 > > > > Il giorno mar 8 feb 2022 alle ore 12:18 Christophe Bornet < > > bornet.ch...@gmail.com> ha scrit

Re: JDK 17 runtime compatibility

Big +1 Le lun. 14 févr. 2022 à 14:54, Nicolò Boschi a écrit : > Dear Pulsar community, > > > I would like to start a discussion about having a plan to make Pulsar > runtime-compatible with JDK 17. > > > The goal is to run Pulsar using JDK17 at runtime, benefitting from the > latest JVM

[DISCUSS] PIP 141 : Pulsar BOM

Hi everyone, I'd like to open a discussion on PIP 141 : Pulsar BOM The PIP is here : https://github.com/apache/pulsar/issues/14168 ## Motivation When designing NAR modules loaded by Nifi in the broker such as protocol handlers, proxy extensions, Pulsar IO connectors, etc..., it's important

Maven wrapper

Hi folks, Some time ago, I opened a PR to add the maven wrapper: https://github.com/apache/pulsar/pull/10487 This has some advantages as we can select a working version of Maven and avoid having to patch it like what we had to do in the past (see

Re: [ANNOUNCE] New PMC Member - Lari Hotari

Congrats Lari ! Le lun. 17 janv. 2022 à 21:50, Dave Fisher a écrit : > Hi - > > The Apache Pulsar Project Management Committee (PMC) has invited Lari > Hotari > (https://github.com/lhotari) as a member of the PMC and we are pleased to > announce that he has accepted. > > He is very active in

  1   2   >