Re: [DISCUSSIONS] Should we use AUTO_PRODUCE schema?

roducer.send(msg0); // validation happens at the producer side > ``` > > ``` > var msg = consumer.receive(); > var student = msg.getValue(); // validation happens again, though it > has already been validated before > ``` > > Thanks, > Yunze > > On Wed, Dec 1

Re: [DISCUSSIONS] Should we use AUTO_PRODUCE schema?

nc(); > ``` > > There are two benefits: > 1. It's clear that the message validation happens before sending. > 2. If users don't want to validate before sending, they can choose to > send the bytes directly and validate the message during consumption. > > The perform

Re: [DISCUSSIONS] Should we use AUTO_PRODUCE schema?

Yunze Xu 于2022年12月14日周三 12:40写道： > > > the user only creates one producer to send all Kafka topic data, if > using Pulsar schema, the user needs to create all schema producers in > a map > > It doesn't make sense to me. If the source topic has messages of > multiple schemas, why did you try to sin

Re: [DISCUSSION] Any idea about simplify the configuration file?

> As more people joined the development of Pulsar and more PIPs are > opened, I found the configurations became very large. At the moment > for commit 9917aac, there are 426 configuration items in broker.conf, > which is too many. I agree with you, the configuration of pulsar is too complicated, we

Re: [DISCUSSION] Any idea about simplify the configuration file?

> As more people joined the development of Pulsar and more PIPs are > opened, I found the configurations became very large. At the moment > for commit 9917aac, there are 426 configuration items in broker.conf, > which is too many. I agree with you, the configuration of pulsar is too complicated, we

Re: [DISCUSSIONS] Should we use AUTO_PRODUCE schema?

Hi, Yunze: Yunze Xu 于2022年12月14日周三 02:26写道： > First, how do you guarantee the schema can be used to encode the raw > bytes whose format is unknown? I think this is what the user needs to ensure that the user knows all the schema from the Kafka topic and the date(bytes[]) that the user can send w

[VOTE] Pulsar Release 2.9.4 Candidate 3

This is the third release candidate for Apache Pulsar, version 2.9.4. This release contains 319 commits by 69 contributors. https://github.com/apache/pulsar/compare/v2.9.3...v2.9.4-candidate-3 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours ***

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

Hi, Donglai: I agree to forbid users to upload `BYTES`. Otherwise, It will cause inconsistent behavior with the pulsar client. Users uploading bytes schema does not have any effect, on the contrary, it will bring a lot of confusion to users. Thanks, bo labuladong 于2022年12月9日周五 18:57写道： > > Hi p

Re: [VOTE] Pulsar Release 2.9.4 Candidate 2

https://github.com/apache/pulsar/pull/18812 This pr is a regression for branch-2.9, so I close 2.9.4 Candidate 2 and will create a new Candidate 3. Please don't validate this candidate. 丛搏 于2022年12月11日周日 15:10写道： > > This is the second release candidate for Apache Pulsar, ve

[VOTE] Pulsar Release 2.9.4 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.9.4. This release contains 317 commits by 69 contributors. https://github.com/apache/pulsar/compare/v2.9.3...v2.9.4-candidate-2 *** Please download, test and vote on this release. This vote will stay open for at least 72 hours ***

Re: [DISCUSS] Modify MessageIdImpl and BatchMessageIdImpl compareTo(MessageId o) method

t; > If users touch the case, the MessageId object must be created > manually, which is a hack. The "wrong" behavior might be used. So my > perspective is that we should not change this behavior. > > Thanks, > Yunze > > On Thu, Dec 8, 2022 at 5:36 PM 丛搏 wrote: > &

Re: [DISCUSS] Modify MessageIdImpl and BatchMessageIdImpl compareTo(MessageId o) method

Hi, all: does anyone have any suggestions? Thanks, bo 丛搏 于2022年11月21日周一 18:57写道： > > Hello, Pulsar community: > > now when `BatchMessageIdImpl` and `MessageIdImpl` with the same > `ledgerId` and `EntryId`, one of it compare with the other, the > `BatchMessageIdImpl` will alwa

Re: [DISCUSS] Transactions isolation design

Hi, All: For question 1: The transaction itself is likely to be executed across multiple tenants. Applying for `TxnID` does not mean that it belongs to a specific tenant (or namespace). It means that it cannot be completely isolated. TC in the tenant will store another tenant topic register consume

Re: [DISCUSS] PIP-227: New API for closing the consumer after waiting for the job to complete

Hi, Jie: I think it's better to leave it to user handle. We try not to add APIs that users can handle themselves. And I don't think there are many scenarios using this API, which brings about higher complexity. I tend to add a new interface beforeClose() in ConsumerInterceptor to allow users to cus

Re: [DISCUSS] Enable branch-2.9 force push and frozen branch-2.9

+3 binding(Penghui Li, JiWei guo, Hang Chen) +2 nonbing(Zike Yang, Yubiao Feng), so I will close this discussion and merge https://github.com/apache/pulsar/pull/18623. thanks for your votes. Thanks, bo 丛搏 于2022年11月25日周五 18:55写道： > > > > > One thing I'd like to make clear:

Re: [DISCUSS] Enable branch-2.9 force push and frozen branch-2.9

> > One thing I'd like to make clear: this is a temporary solution, and we'll > re-enable branch protection after the actions are performed (or relax to > 2.9.4 released). yes, after this pr: https://github.com/apache/pulsar/pull/18623 merged and reset branch-2.9 to commit 5ed247de3a, I will push

Re: [VOTE] Pulsar Release 2.9.4 Candidate 1

Hi, all: this candidate cancel , reason:https://lists.apache.org/thread/jcrq9q0k6kh9rvb71dwb9s3mvo5c5dk5 丛搏 于2022年11月24日周四 11:22写道： > > Docker images: > https://hub.docker.com/layers/congbobo184/pulsar-all/2.9.4/images/sha256-53ef82d20fa7d9ee4809a3480f98cacea9b608cbb3a428881bcad3b

[DISCUSS] Enable branch-2.9 force push and frozen branch-2.9

Hi, pulsar community, I am sorry for that, there is no commit to execute cherry-pick --continue, resulting in many cherry-pick commit messages not being correct[1]. So re-cherry-pick, now requires enabling branch-2.9 force push and frozen branch-2.9. reset commit 5ed247de3a. now branch-2.9 has c

Re: [DISCUSS] The use of consumer redeliverUnacknowledgedMessages method

Hi, Joe: > This "brokenness" is not clear to me. https://github.com/apache/pulsar/pull/10478 This PIP solves some problems of "brokenness", >The sequence 3,4,5,6,7,8,9,10,11 12,13,14,15, 16 ,9,10,11,12,13,14,15,16,17, >18, 19, 20 ...does not break > the ordering guarantees of Pulsar If don't use

Re: [DISCUSS] The use of consumer redeliverUnacknowledgedMessages method

Hi, Baodi > After, when the user calls `redeliverUnacknowledgedMessages` under failover > and exclusive subType, > It gets a warning reminder that the messages may be out of order, right? > yes, in failover and exclusive subType, we should suggest user to use a new API to redeliver the messages a

Re: [VOTE] Pulsar Release 2.9.4 Candidate 1

download the source package, and follow the Release Candidate Validation[1] to validate the release https://pulsar.apache.org/contribute/validate-release-candidate/ 丛搏 于2022年11月24日周四 11:11写道： > > This is the first release candidate for Apache Pulsar, version 2.9.4. > > It fixes the foll

[VOTE] Pulsar Release 2.9.4 Candidate 1

This is the first release candidate for Apache Pulsar, version 2.9.4. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.9.4+ *** Please download, test and vote on this release. This vote will stay open for at least 72 hours *** Note t

Re: [DISCUSS] The use of consumer redeliverUnacknowledgedMessages method

an > modify it to be synchronous and support retrying. > > > > Thanks, > Baodi Shi > > > 2022年11月21日 21:03，丛搏 写道： > > > > Hello, Pulsar community: > > > > Now client consumer `void redeliverUnacknowledgedMessages();` is an > > async interf

[DISCUSS] The use of consumer redeliverUnacknowledgedMessages method

Hello, Pulsar community: Now client consumer `void redeliverUnacknowledgedMessages();` is an async interface, but it doesn't have the return value. only `writeAndFlush` the redeliver command then finishes. `ConsumerImpl`: https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/or

[DISCUSS] Modify MessageIdImpl and BatchMessageIdImpl compareTo(MessageId o) method

Hello, Pulsar community: now when `BatchMessageIdImpl` and `MessageIdImpl` with the same `ledgerId` and `EntryId`, one of it compare with the other, the `BatchMessageIdImpl` will always be greater than MessageIdImpl. see : https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/o

Re: [DIDSCUSS] Realease Pulsar 2.9.4 cherry-pick done

/pulsar/pull/18454, which has already been > cherry-picked. > > Thanks, > Yunze > > On Thu, Nov 17, 2022 at 8:26 PM 丛搏 wrote: > > > > Hello, Pulsar community: > > > > The cherry-pick of 2.9.4 is basically completed. > > Contains about 300+ PRs. >

[DIDSCUSS] Realease Pulsar 2.9.4 cherry-pick done

Hello, Pulsar community: The cherry-pick of 2.9.4 is basically completed. Contains about 300+ PRs. link: https://github.com/apache/pulsar/pulls?q=is%3Apr+label%3Arelease%2F2.9.4 If you still have a pr that must be released in pulsar-2.9.4, please reply to me or ping me on GitHub. Thanks, Bo

Re: Data quality problem

hi, Devin: the first Kafka doesn't support schema. `confluent `does. pulsar schema supports validation and versioning. Are you encountering a schema version caused by automatic registration, and the data source is not clear? I think you can turn off the producer's automatic registration schema, and

Re: [DISCUSSION] Support seek and ack multiple MessageIds

Hi Yunze, Yunze Xu 于2022年11月10日周四 20:17写道： > ```java > Map> seekAsync(Map > messageIdMap); > Map> acknowledgeAsync(Map MessageId> messageIdMap); > Map> > acknowledgeCumulativeAsync(Map messageIdMap); > ``` why not add the method using `String topicName directly, MessageId msgId` directly? like:

Re: [DISCUSS] PIP-218: Consumer batchReceive() single partition every receive

21:30写道： > > Ok. > > I would list what you wrote in your original PIP for context. > > What is your future improvement you plan? > > On Thu, Nov 3, 2022 at 11:46 AM 丛搏 wrote: > > > Good question! > > It is a scene for our subsequent optimization, and we

Re: [VOTE] PIP-219: Support full scan and trim ledger

+1(non-binding) Thanks, Bo PengHui Li 于2022年11月6日周日 09:26写道： > > +1 > > Penghui > > linlin 于2022年11月1日 周二22:28写道： > > > Hi folks, > > > > I'd like to start a vote for the PIP-219: Support full scan and trim ledger > > ( > > https://github.com/apache/pulsar/issues/18128) > > > > The discussion ca

Re: [DISCUSS] PIP-218: Consumer batchReceive() single partition every receive

are many partitions. In this scenario, this method may have a large delay. > > On Thu, Oct 27, 2022 at 3:36 PM Haiting Jiang > wrote: > > > +1 > > > > Haiting > > > > On Thu, Oct 27, 2022 at 5:55 PM Yubiao Feng > > wrote: > > > > > >

Re: [VOTE] PIP-218: Consumer batchReceive() single partition every receive

; > > > > > Thanks, > > > Haiting > > > > > > On Fri, Oct 28, 2022 at 10:43 AM Yunze Xu > > > wrote: > > > > > > > > +1 (non-binding) > > > > > > > > Thanks, > > > > Yunze > > > >

[DISCUSS] Release Pulsar 2.9.4

Hello, Pulsar community: I'd like to propose releasing Apache Pulsar 2.9.4. It's been about three months since 2.9.3 was released. There are 123 PRs [0] needed to cherry-pick in branch-2.9. I will cherry-pick these PRs for branch-2.9. Exclude some PRs that merge directly into branch-2.9. There a

Re: [DISCUSS] PIP-215: Configurable Topic Compaction Strategy

+1(non-binding) thanks, bo Heesung Sohn 于2022年10月19日周三 07:54写道： > > Hi pulsar-dev community, > > I raised a pip to discuss : PIP-215: Configurable Topic Compaction Strategy > > PIP link: https://github.com/apache/pulsar/issues/18099 > > Regards, > Heesung

[VOTE] PIP-218: Consumer batchReceive() single partition every receive

Hi, pulsar community: I start a PIP about `User-friendly acknowledgeCumulative API on a partitioned topic or multi-topics` discuss thread: https://lists.apache.org/thread/30rwksz4gmvgspkgcfsk708sgb1n7vbo https://lists.apache.org/thread/k090ftlqc149yr1cnprxb29vxg160131 PIP: https://github.com/apa

[DISCUSS] PIP-218: Consumer batchReceive() single partition every receive

Hi, pulsar community: I start a PIP about `User-friendly acknowledgeCumulative API on a partitioned topic or multi-topics` discuss thread: https://lists.apache.org/thread/30rwksz4gmvgspkgcfsk708sgb1n7vbo https://lists.apache.org/thread/k090ftlqc149yr1cnprxb29vxg160131 PIP: https://github.com/apa

Re: [VOTE] PIP-212: Default reppDnsResolverClass to ZkBookieRackAffinityMapping

+1 (non-binding) Thanks, bo Enrico Olivelli 于2022年10月21日周五 14:57写道： > > +1 (binding) > > Enrico > > Il giorno ven 21 ott 2022 alle ore 08:07 Michael Marshall > ha scritto: > > > > Bump. In my opinion, this is a bug that we need to fix before any new > > releases. It is only a PIP because fixing

Re: PIP-Java Client support to Cumulative Acknowledge messages for multiple partitions or topics

queue, using ConsumerImpl.batchReceive() directly when use MultiTopicsConsumerImpl.batchReceive() Thanks, bo Enrico Olivelli 于2022年10月20日周四 17:37写道： > > Il giorno gio 20 ott 2022 alle ore 11:09 丛搏 ha scritto: > > > > Hi, > > > > I have another solution, we only

Re: [ANNOUNCE] Haiting Jiang as a new PMC member in Apache Pulsar

Congratulations, Haiting! Thanks, bo PengHui Li 于2022年10月20日周四 16:55写道： > > Congratulations, Haiting! > > Best, > Penghui > > On Thu, Oct 20, 2022 at 9:53 AM Jun Ma wrote: > > > Congratulations, Haiting! > > > > > > Best, > > Jun > > > > From: Yunze Xu > > Sent

Re: PIP-Java Client support to Cumulative Acknowledge messages for multiple partitions or topics

Hi, I have another solution, we only guarantee the invoke batch receive returns the messages are the same topic message. In this way, we don't need to add the new API for ack. use example is: ``` // consumer the multi-partition messages while (true) { Messages messages = consumer.batchReceive(

Re: [DISCUSS] PIP-215: Configurable Topic Compaction Strategy

Hi, Heesung: I have some doubts. I review your PIP-192: New Pulsar Broker Load Balancer. I found that unload topic uses the leader broker to do, (Assigning, Return) uses the lookup request broker. why (Assigning, Return) not use a leader broker? I can think of a few reasons: 1. reduce leader broker

Re: [DISCUSS] Update schema authentication permission issue

Hi Enrico: Enrico Olivelli 于2022年10月13日周四 17:31写道： > > Bo, > > Il giorno gio 13 ott 2022 alle ore 06:00 丛搏 ha scritto: > > > > Hello, Pulsar community: > > > > Now, we have two authentications for updating the schema > > 1. producer and consumer

[DISCUSS] Update schema authentication permission issue

Hello, Pulsar community: Now, we have two authentications for updating the schema 1. producer and consumer can update the schema using TopicOperation produce or consume when open autoUpdateSchema 2. pulsar admin uses Tenant authentication This will produce problems when using different authentica

[DISCUSS] Use AUTO_CONSUME schema with Avro logical type conversion problem

Hello, Pulsar community: Now, we use Avro Schema with Logical type, and the client automatically adds logical type conversion. You can see PR https://github.com/apache/pulsar/pull/6704. But AUTO_CONSUME Schema with Avro doesn't add the logical type conversion. It makes the Time type decode to L

Re: [DISCUSS] Consumer reconnection causes repeated consumption messages

a valid message, and they can even be > created directly by the user. > > Thanks, > Haiting > > On Wed, Sep 14, 2022 at 8:34 PM 丛搏 wrote: > > > > Hi Haiting, Michael , > > > > I tested an example, and there may be some problems when using the sub > > reset

Re: [DISCUSS] Consumer reconnection causes repeated consumption messages

> And I am not sure if there are other operations that would reset the > > cursor implicitly. > > > > Thanks, > > Haiting > > > > On Thu, Sep 8, 2022 at 11:36 PM 丛搏 wrote: > > > > > > Hi Haiting > > > > > > When using cumu

Re: [DISCUSS] Consumer reconnection causes repeated consumption messages

Hi all, you can see the problem in a google doc and comments. google doc link: https://docs.google.com/document/d/1J1xGcj8YORrdlCa_XDt28uV0TMp03gSmX_z43ZRhwZo/edit?usp=sharing Thanks! Bo 丛搏 于2022年9月8日周四 10:55写道： > > Hello, Pulsar community: > > > Now the consumer does not filte

Re: [DISCUSS] Consumer reconnection causes repeated consumption messages

we should be careful of any operations that would reset the cursor. > > For example, if the user resets the cursor with the admin client. We > > need more detail info on this matter. > > And I am not sure if there are other operations that would reset the > > cursor implicitly.

Re: [DISCUSS] Consumer reconnection causes repeated consumption messages

re detail info on this matter. > And I am not sure if there are other operations that would reset the > cursor implicitly. > > Thanks, > Haiting > > On Thu, Sep 8, 2022 at 11:36 PM 丛搏 wrote: > > > > Hi Haiting > > > > When using cumulative ack, we

Re: [VOTE] PIP-196 Segmented transaction buffer snapshot

Hi, Xiangying +1(non-binding) This PIP overall LGTM! It solves the problem of snapshots not being able to scale. We can make some optimizations later : 1. Merge transaction snapshot segments to reduce the number of segments and the index's size. 2. Add snapshot segments to memory as TB requires re

Re: [DISCUSS] Consumer reconnection causes repeated consumption messages

; point of user explicit acking. > > Thanks, > Haiting > > On Thu, Sep 8, 2022 at 10:56 AM 丛搏 wrote: > > > > Hello, Pulsar community: > > > > > > Now the consumer does not filter messages that have already been > > consumed. After con

[DISCUSS] Consumer reconnection causes repeated consumption messages

Hello, Pulsar community: Now the consumer does not filter messages that have already been consumed. After consumer reconnection, the broker will dispatch messages to the consumer from the markDeletePosition. In Failover and Exclusive subscription type, all messages in a topic will be dispatched t

Re: [DISCUSSION] PiP196 TransactionBuffer Multiple-snapshots

Hi Xiangying I think this is a very good optimization solution, it solves the problem that users have a lot of aborted transactions. Thanks! Bo Yubiao Feng 于2022年8月16日周二 11:33写道： > > Hi Xiangying > > >> Can the sequence id generation strategy be added to the proposal？ > > > think it's an imple

Re: [DISCUSS] Move PIPs to the codebase?

Hi all, I also think it's a good idea. Not only can it prevent the duplication of PIP numbers, but most importantly, it is easier to annotate, in other words, It can review the PIP just like the review code, it can make the problem more focused, and it is easier for the viewer to annotate at any t

Re: [VOTE] [PIP-153] Optimize metadataPositions in MLPendingAckStore

+1 Thanks, Bo PengHui Li 于2022年5月11日周三 15:52写道： > > +1 > > Penghui > > On Mon, Apr 25, 2022 at 2:55 PM 一苇以航 <1984997...@qq.com.invalid> wrote: > > > Hi Pulsar Community. > > > > This is the voting thread for PIP-153. It will stay open for at least 48 > > hours. > > > > The proposal can be found:

Re: [DISCUSSION] PIP-156: Enable system topic by default

+1 Thanks, Bo Haiting Jiang 于2022年4月27日周三 10:39写道： > > +1 > > Thanks, > Haiting > > On 2022/04/26 12:07:32 guo jiwei wrote: > > Hi community: > >In PIP-39 > > , > > we have introduced namespace event to support topic le

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

Hi Pulsar community, This PIP has been voted, and has three bindings. voting list : https://lists.apache.org/thread/ql6ksch1dszqcqnw3yhhwxcj5cxjw2gx so close this PIP Thanks, Bo

Re: Call for projects and mentors for OSPP 2022

Thanks all, here is my application: Project Name: Support Pulsar Transaction Buffer multi snapshot Project Description: Now the pulsar transaction buffer is recovered by one snapshot, this snapshot is an entry. When the number of abort txns is too many, the size of this snapshot will exceed the s

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

t; > 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: > > pi

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

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

Re: [DISCUSS] [PIP-153] Optimize metadataPositions in MLPendingAckStore

+1 link : https://github.com/apache/pulsar/issues/15073 Thanks! Bo xiangying Meng <1984997...@qq.com.invalid> 于2022年4月11日周一 17:27写道： > > Hi Pulsar community, > > > I create a PIP to optimize metadataPosition in MLPendingAckStore to use less > memory and avoid OOM. > The proposal can be > found

[DISCUSS] [Transaction] Clear namespace backlog can't clear system topic and system sub backlog.

Hi : issue link : https://github.com/streamnative/support-tickets/issues/408 # Background Now we have many clear namespace backlog interfaces etc. ``` clearNamespaceBacklog(String namespace) clearNamespaceBacklogAsync(String namespace

[DISCUSS]

Hi Pulsar Community, We found some problems in the transaction coordinator load mechanism. For details, please see: https://github.com/apache/pulsar/issues/12129 Thanks. Bo

PIP 95: Transaction coordinator loading mechanism.

Hello: We are sorry that there is an error in the existing transaction coordinator load mechanism, which will cause the transaction coordinator to be unavailable. I created a PIP 95: Transaction coordinator loading mechanism.(https://github.com/apache/pulsar/wiki/PIP-95:-Transaction-coordinator-lo

[DISCUSS] PIP 84 : Transaction performance tools.

Hello, How are you? We have created a PIP. PIP 92: Topic policy across multiple clusters https://github.com/apache/pulsar/wiki/PIP-93%3A-Transaction-performance-tools If you have any suggestions or ideas about this PIP, please discuss it in this email Thanks, Bo Cong

[ANNOUNCE] Apache Pulsar 2.7.3 released

The Apache Pulsar team is proud to announce Apache Pulsar version 2.7.3. 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 management for subsc

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

Enrico, Sorry I read it wrong. I will fix the branch-2.7 build test after I release v2.7.3. Thanks for your advice. Tranks, Bo Enrico Olivelli 于2021年8月4日周三 下午3:30写道： > Il Mer 4 Ago 2021, 04:49 丛搏 ha scritto: > > > The vote passes with the following votes: > > - Yong

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

roll a new > >> release. > >> > >> There is no hurry to approve a release. > >> > >> In Apache we are primarily releasing the sources and the binaries are > >> provided only 'for convenience'. > >> > >> So users are

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

tps://github.com/apache/pulsar/pull/11294> don't have cherry-pick to branch-2.7. I suggest moving it to 2.7.4 to fix. Because it is not a newly introduced problem, but an existing problem. Thanks! Bo Enrico Olivelli 于2021年7月28日周三 下午2:03写道： > Il giorno mer 28 lug 2021 alle or

Re: [VOTE] Pulsar Release 2.7.3 Candidate 2

; > > > > > - Checked checksums and signatures > > > - Compiled the source > > > - Ran the standalone server > > > - Confirmed that producer and consumer work properly > > > - Confirmed that the sample function works properly > > > > > &

Re: [VOTE] Pulsar Client Go Release 0.6.0 Candidate 1

+1 Regards, Bo r...@apache.org 于2021年7月21日周三 下午3:34写道： > Hi everyone, > > > Please review and vote on the release candidate #1 for the version 0.6.0, > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > This is the first r

[VOTE] Pulsar Release 2.7.3 Candidate 2

This is the second release candidate for Apache Pulsar, version 2.7.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.3+is%3Apr+ *** Please download, test and vote on this release. This vote will stay open for at least 72 hours ***

[VOTE] Pulsar Release 2.7.3 Candidate 1

This is the first release candidate for Apache Pulsar, version 2.7.3. It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Aopen+label%3Arelease%2F2.7.3+is%3Apr+ *** Please download, test and vote on this release. This vote will stay open for at least 72 hours ***

[DISCUSS] Apache Pulsar 2.7.3 Release

Hi all, How are you? I think you must be doing well. It has been two months since we released the Apache Pulsar 2.7.2. We have a lot of fixes already merged. So I would like to start to prepare our next patch release in the next few days. You can find the whole change list of the 2.7.3 release f

[DISCUSS] PIP 84 : Pulsar client: Redeliver command add epoch.

Hello, We have created a PIP-84 for Pulsar client: Redeliver command add epoch. https://github.com/apache/pulsar/wiki/PIP-84-%3A-Pulsar-client%3A-Redeliver-command-add-epoch. Thanks, Bo Cong

Re: [VOTE] Pulsar Client Go Release 0.4.0 Candidate 1

+1 On 2021/02/09 05:46:48, xiaolong ran wrote: > Hi everyone,> > Please review and vote on the release candidate #1 for the version 0.4.0, as > follows:> > [ ] +1, Approve the release> > [ ] -1, Do not approve the release (please provide specific comments)> > > This is the first release ca

Re: Virtual Pulsar Community Meetings

+1 On 2021/01/29 08:53:40, Sijie Guo wrote: > That's a super great idea! Thank you for bringing this up! > > Given there are a lot of committers/contributors are from North America and > Asia, I think we should pick up a better time that would be suitable for > people from Asia (Japan and China

Re: [VOTE] Pulsar Release 2.7.0 Candidate 1

+1 (no-binding) - Validate Connectors - Validate Pub/Sub and Java Functions - Validate Stateful Functions Thanks, Bo Cong > 2020年11月23日 上午8:31，PengHui Li 写道： > > This is the first release candidate for Apache Pulsar, version 2.7.0. > > It fixes the following > issues:https://github.com/apache

Re: [VOTE] Pulsar Client Go Release 0.1.1 Candidate 1

+1 (non-binding) > 2020年6月18日 上午11:02，PengHui Li 写道： > > +1 (binding)

Re: [VOTE] Pulsar Client Go Release 0.1.0 Candidate 1 again

+1 Thanks BO CONG xiaolong ran 于2020年3月31日周二 上午11:02写道： > Hi everyone, > > Please review and vote on the release candidate #1 for the version 0.1.0, > as follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the first release

Re: [VOTE] Pulsar Client Go Release 0.1.0 Candidate 1

+1 good work! On 2020/03/25 05:43:04, xiaolong ran wrote: > Hi everyone, > > Please review and vote on the release candidate #1 for the version 0.1.0, as > follows: > [ ] +1, Approve the release > [ ] -1, Do not approve the release (please provide specific comments) > > This is the first rel

Re: [Discuss] Create the first release of Apache Pulsar-client-go

+1, I agree with you to release it. Thanks, Bo Cong On 2020/03/20 11:22:03, xiaolong ran wrote: > Hello committers, > > Since: > - A lot of users use > [pulsar-client-go](https://github.com/apache/pulsar-client-go > ) and many > of them want

Re: [ANNOUNCE] new committer: Yu Liu

Congratulations Yu Liu! Bo Cong PengHui Li 于2019年12月3日周二 下午2:15写道： > Hi everyone, > > The Project Management Committee (PMC) for Apache Pulsar > > has invited Yu Liu to become a committer and we are pleased > > to announce that her has accepted. > > Yu has done good contribution to Apache Pulsa

Re: [VOTE] Pulsar Release 2.4.2 Candidate 3

+1 (non-bind) Validate checksum Validate the binary distribution Validate Pub/Sub and Java Functions Validate Connectors Validate Stateful Functions Validate RPM and DEB packages mvn apache-rat:check xiaolong ran 于2019年11月29日周五 下午3:41写道： > Hi everyone, > > This is the third release candidate for

Re: [VOTE] Pulsar Release 2.4.2 Candidate 2

+1 (non-bind) https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Validate checksum Validate the binary distribution Validate Pub/Sub and Java Functions Validate Connectors Validate Stateful Functions Validate RPM and DEB packages Thanks, Bo Cong Sijie Guo 于2019年11月28日周四 上午2:46写道：

Re: [VOTE] Pulsar Release 2.4.2 Candidate 1

+1 (non-bind) https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Validate checksum Validate the binary distribution Validate Pub/Sub and Java Functions Validate Connectors Validate Stateful Functions Validate RPM and DEB packages Thanks! -- Bo Cong xiaolong ran 于2019年11月22日周五 上午11

Re: [VOTE] Pulsar Release 2.4.2 Candidate 1

+1 (non-bind) https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Validate checksum Validate the binary distribution Validate Pub/Sub and Java Functions Validate Connectors Validate Stateful Functions Validate RPM and DEB packages Thanks! -- Bo Cong Guangning E 于2019年11月22日周五 下午1:1

Re: [REVOTE] PIP-47: Time Based Release Plan

+1 (non-binding) On 2019/11/11 02:16:23, xiaolong ran wrote: > Hello everyone:> > > Please review and vote on the PIP-47 propose:> > https://github.com/apache/pulsar/wiki/PIP-47%3A-Time-Based-Release-Plan > > > > > Abo

<    1   2