Re: LastMessageId - again

Great, thank you Matteo and Sijie, last questionfrom org.apache.pulsar.client.api.Reader interface...is there any way to get the internal subscription id. I guess I should perform the following steps: 1) creare a Reader 2) get subscription id 3) move the reader to my current message id 4) use

Re: LastMessageId - again

The reader has indeed already a "dummy" ephemeral subscription. As long as it's connected, the backlog for the reader is reported. -- Matteo Merli On Mon, Jul 22, 2019 at 7:26 AM Enrico Olivelli wrote: > > Sijie, > > Il lun 22 lug 2019, 15:50 Sijie Guo ha scritto: >> >> You can query the topi

Re: LastMessageId - again

Sijie, Il lun 22 lug 2019, 15:50 Sijie Guo ha scritto: > You can query the topic stats. There is a "backlog" field in topic stats. > It will tell you how many messages that a subscription has not consumed. It > is similar as consumer lag in Kafka. > Actually I don't have a subscription to the t

Re: LastMessageId - again

You can query the topic stats. There is a "backlog" field in topic stats. It will tell you how many messages that a subscription has not consumed. It is similar as consumer lag in Kafka. Thanks, Sijie On Mon, Jul 22, 2019 at 6:46 PM Enrico Olivelli wrote: > Hello, > > I am looking for a functio

LastMessageId - again

Hello, I am looking for a function in Pulsar API to get the current consumer "lag" I see that Pulsar recently added getLastMessageId API but this is not useful to me https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId In Pulsar if you have two message ids you cannot compute any

Slack digest for #general - 2019-07-22

2019-07-21 17:55:38 UTC - mapa: @mapa has joined the channel 2019-07-21 17:58:28 UTC - mapa: does pulsar have altrnative for kstream 2019-07-21 17:58:29 UTC - mapa: ? 2019-07-21 18:00:59 UTC - David Kjerrumgaard: @mapa I would recommend looking at Heron Streamlets for this.