Re: [VOTE] [PIP-154] Max active transaction limitation for transaction coordinator
+1 Regards Jiwei Guo (Tboy) On Wed, Apr 27, 2022 at 10:52 AM Jiuming Tao wrote: > +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 > >
?????? [VOTE] [PIP-154] Max active transaction limitation for transaction coordinator
+1 Thanks, Xiangying Meng -- -- ??: "dev" https://github.com/apache/pulsar/issues/15133 > > > > Discuss thread: > https://lists.apache.org/thread/h8gzgs78bm4pzy2rjtgvvmo1jbzttcx8 > > > > Thanks, > > Bo > >
[GitHub] [pulsar-client-node] massakam merged pull request #210: Bump grunt from 1.4.1 to 1.5.2
massakam merged PR #210: URL: https://github.com/apache/pulsar-client-node/pull/210 -- 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-150] Support read the message of startMessageId position on the broker side
+1 (non-binding) Thanks, Zike On Wed, Apr 27, 2022 at 10:44 AM Lin Lin wrote: > > +1 > > Lin Lin
Re: [ANNOUNCE] New Committer: Nicolò Boschi
Congrats, Nicolò! Best, Zike On Wed, Apr 27, 2022 at 2:34 PM Enrico Olivelli wrote: > > 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 > > > > > > > > > >
Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side
Thanks for your vote! Closed by 3 (+1) binding vote and 0 (-1) vote.
Thanks,
Zixuan
Zixuan Liu 于2022年4月6日周三 16:54写道：
> Hi Pulsar community,
>
> Start voting for PIP-150: https://github.com/apache/pulsar/issues/14883
>
> Thanks,
> Zixuan
>
> -
>
> Discussion thread:
> https://lists.apache.org/thread/n3drk2g2oy766qnbtx17knvtssy3tdyl
>
> ## Motivation
>
> Currently, the Pulsar-client supports setting the `startMessageId` for
> Consumer and Reader, and also supports reading the message of
> `startMessageId` position.
>
> Assume, we have two message id 1,2,3,4 in the topic:
>
> - When we set `earliest` as `startMessageId` value, we can get the message
> of message id 1
> - When we set `latest` as `startMessageId` value, we can't get any message
>
> Sometimes we want to read the message id 4 for the first time, we have
> only one approach in client:
>
> ```
> Reader reader = pulsarClient.newReader()
> .topic(topicName)
> .subscriptionName(subscriptionName)
> .startMessageId(MessageId.latest)
> .startMessageIdInclusive()
> .create();
>
> reader.hasMessageAvailable();
> Message msg = reader.readNext(1, TimeUnit.SECONDS);
> ```
>
> Call `reader.hasMessageAvailable()` before `reader.readNext()` can get the
> correct message id 4, which include seek action when the
> `startMessageIdInclusive()` is enabled.
>
> This approach is confusing. If we do this on the broker side, it will
> make things easier.
>
> ## Goal
>
> This PIP proposes support for reading the message of `startMessageId`
> position on the broker side:
>
> - Add to `Consumer`
> - Add to `Reader`
>
> ## Implementation
>
> ### Protocol
>
> Add a `start_message_id_inclusive` field to `CommandSubscribe` for
> determine whether to read the message of `startMessageId` position:
>
> ```
> message CommandSubscribe {
> // some fields
>
> // If specified, the subscription will read the message from the start
> message id position.
> optional bool start_message_id_inclusive = 20 [default = false];
> }
> ```
>
> ### ManagedCursorImpl
>
> Add a check in
> `org.apache.bookkeeper.mledger.impl.ManagedCursorImpl#initializeCursorPosition`.
>
>
> We only need to care that the `startMessageId` is `MessageId.latest` and
> the`start_message_id_inclusive` is `true`, we get latest position from
> ledger as `readPosition` value, otherwise if
> the`start_message_id_inclusive` is `false`, get next position of the
> latest position as `readPosition` value.
>
> ### Client
>
> The `Consumer` and `Reader` support setting the
> `start_message_id_inclusive` value to `CommandSubscribe` command.
>
> ### Compatibility
>
> This feature can have both backward and forward compatibility, this means
> the users can use any client to request any broker.
>
> Notice that the users still can read the message of the latest position by
> call `reader.hasMessageAvailable()` before `reader.readNext()`, but this
> call can be ignored when using the new client and the new broker.
>
>
>
>
Re: [ANNOUNCE] New Committer: Nicolò Boschi
Congratulations, Nicolò. Zike Yang 于2022年4月27日周三 17:41写道： > Congrats, Nicolò! > > Best, > Zike > > On Wed, Apr 27, 2022 at 2:34 PM Enrico Olivelli > wrote: > > > > 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 < > jianghait...@apache.org> > > > > > 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-site] Anonymitaet opened a new pull request, #60: [improve][website] Update Ecosystem Page Intro
Anonymitaet opened a new pull request, #60: URL: https://github.com/apache/pulsar-site/pull/60 Preview looks good:  -- 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
youg9203 commented on issue #78: URL: https://github.com/apache/pulsar-helm-chart/issues/78#issuecomment-1110962699 Yeah, that worked, thanks -- 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: Call for Presentations now open, ApacheCon North America 2022
Just wanted to put this back at the top of your email. The CFP for Apache Con is open and there is a two day Pulsar track! The cut off date is fast approaching. https://www.apachecon.com/acna2022/ On Wed, Mar 30, 2022 at 10:48 AM Dave Fisher wrote: > The Call For Presentations for ApacheCon NA in New Orleans is now open. > > There will be a Pulsar Event Streaming track. Please consider attending > and submitting a talk. > > This will be an in-person conference only. > > Further details will come as we get closer to the event. > > All The Best, > Dave > > > Begin forwarded message: > > > > From: Rich Bowen > > Subject: Call for Presentations now open, ApacheCon North America 2022 > > Date: March 30, 2022 at 5:16:06 AM PDT > > To: annou...@apachecon.com > > > > [You are receiving this because you are subscribed to one or more user > > or dev mailing list of an Apache Software Foundation project.] > > > > ApacheCon draws participants at all levels to explore “Tomorrow’s > > Technology Today” across 300+ Apache projects and their diverse > > communities. ApacheCon showcases the latest developments in ubiquitous > > Apache projects and emerging innovations through hands-on sessions, > > keynotes, real-world case studies, trainings, hackathons, community > > events, and more. > > > > The Apache Software Foundation will be holding ApacheCon North America > > 2022 at the New Orleans Sheration, October 3rd through 6th, 2022. The > > Call for Presentations is now open, and will close at 00:01 UTC on May > > 23rd, 2022. > > > > We are accepting presentation proposals for any topic that is related > > to the Apache mission of producing free software for the public good. > > This includes, but is not limited to: > > > > Community > > Big Data > > Search > > IoT > > Cloud > > Fintech > > Pulsar > > Tomcat > > > > You can submit your session proposals starting today at > > > https://urldefense.com/v3/__https://cfp.apachecon.com/__;!!PbtH5S7Ebw!bjHh-7Qs4SC2SrRi3rdy_aIn7ORTAVGBn98VMB-SV-cUn9abtVfRRzXVW6nun5nHqnrtV0DBNgUmZpk9Xg$ > > > > Rich Bowen, on behalf of the ApacheCon Planners > > apachecon.com > > @apachecon > >
[GitHub] [pulsar-site] Anonymitaet commented on pull request #60: [improve][website] Update Ecosystem Page Intro
Anonymitaet commented on PR #60: URL: https://github.com/apache/pulsar-site/pull/60#issuecomment-655895 @dave2wave do you mean **submit new projects to the Ecosystem page** or **contribute (donate) new projects to Pulsar** (similar to https://streamnative.io/blog/tech/2021-06-01-building-connectors-on-pulsar-made-simple/)? If you refer to the former one, we'll document the workflow and inform the community later. -- 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] Anonymitaet merged pull request #60: [improve][website] Update Ecosystem Page Intro
Anonymitaet merged PR #60: URL: https://github.com/apache/pulsar-site/pull/60 -- 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] urfreespace merged pull request #61: fix: some 404 links fix
urfreespace merged PR #61: URL: https://github.com/apache/pulsar-site/pull/61 -- 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
