Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

+1(unbinding) Thanks, Mattison On Mon, 11 Apr 2022 at 13:06, Haiting Jiang wrote: > +1 > > Thanks, > Haiting > > On 2022/04/06 08:54:05 Zixuan Liu wrote: > > Hi Pulsar community, > > > > Start voting for PIP-150: https://github.com/apache/pulsar/issues/14883 > > > > Thanks, > > Zixuan > > > > -

Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

+1 Thanks, Haiting On 2022/04/06 08:54:05 Zixuan Liu wrote: > 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 > > ## Moti

Re: [VOTE] Pulsar Manager Release 0.3.0 Candidate 1

-1(non-binding) I am sorry, I verified it encountered this exception: Caused by: org.apache.calcite.sql.validate.SqlValidatorException: Column 'BOOKIE' not found in any table at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at java.base/jdk.internal.refle

Re: [DISCUSS] markdelete position not moving forward when skipping lost entries

Hi lordcheng, Sorry for the late reply. IMO, from the Pulsar side, we remove a ledger from a topic, not the entry. After I thought about it, I think we should fix the issue from the BookKeeper side. The BookKeeper also don't support delete entries, so if the ledger still there but bookkeeper lose

Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

> regarding the compatibility, should we check the protocol version at the client side? The old version version doesn't support `start_message_id_inclusive` which means the client side still needs to do the seek operation while requesting an old version broker. Oh sorry, my fault. If the broker si

Re: [VOTE] [PIP-150] Support read the message of startMessageId position on the broker side

Hi zixuan, The proposal looks good, regarding the compatibility, should we check the protocol version at the client side? The old version version doesn't support `start_message_id_inclusive` which means the client side still needs to do the seek operation while requesting an old version broker. >

Re: [DISCUSS] [PIP-152] Support subscription level dispatch rate limiter setting.

+1 Penghui On Sat, Apr 9, 2022 at 4:24 PM Haiting Jiang wrote: > Hi Pulsar community, > > I created a PIP to add support for subscription level dispatch rate > limiter setting. > > The proposal can be found: https://github.com/apache/pulsar/issues/15094 > > > > ## Motivation > > Currently,

[GitHub] [pulsar-client-node] hrsakai opened a new pull request, #208: Add a pulsar nodejs client document link to package.json/README

hrsakai opened a new pull request, #208: URL: https://github.com/apache/pulsar-client-node/pull/208 Currently, users can't find https://pulsar.apache.org/docs/en/client-libraries-node on [github](https://github.com/apache/pulsar-client-node) and [npmjs](https://www.npmjs.com/package/pulsar