Hey Team, How exactly should one interpret this statement (source)?

PInot currently relies on Pulsar client version 2.7.2. Users should make sure the Pulsar broker is compatible with the this client version.

Say I have a Pulsar cluster of version 2.4.1 in place already; then I won't be able to consume its traffic with the most up-to-date Pinot binary? Thanks in advance for any help!

@Kartik Khare ^^

Hi Zsolt, Pulsar docs are unclear on the compatibility across different versions. Hence the line was added so that users can verify themselves with a pulsar client 2.7x if it works with their broker or not. Give me a few moments to test it out on my machine

Sure, thank you!

Let’s also add this context in the doc

A bit of extra context about my experiments if it helps: • Pinot is on

0.10.0

• The manually attached (official) Pulsar plugin is on

0.11.0

• Additionally, I set up one more plugin that has a custom decoder class to deal with the Pulsar messages Roughly what I tried: • After sending to Pinot (using the admin tools) the new real-time table configuration (having a Pulsar stream configured), the connection seems to get established (seeing logs from the Pinot Server like:

Connected to server
Starting Pulsar consumer status recorder with config: ...

• Also, the subscription to the desired topic seems OK:

Subscribed to topic on ...
Successfully getLastMessageID xy:-1

• Then, I see something like this twice, which seems a bit strange:

[topic_name][Pinot_subscription_id] Closed consumer
[id: some_id, L:/localhost:port ! R:/cluster/node:port] Disconnected

• A couple of extra error logs then:

Received error from server: Error when resetting subscription: xy:-1
Failed to reset subscription: Error when resetting subscription: xy:-1
Error consuming records from Pulsar topic
org.apache.pulsar.client.api.PulsarClientException: java.util.concurrent.ExecutionException: org.apache.pulsar.client.api.PulsarClientException: Failed to seek the subscription reader-ID of the topic topic_name to the message xy:-1:-1

Hi, is the pulsar topic created a persistent one? I have seen this error happening on non-persistent topics which disappear from pulsar

Thanks for looking into this, Kartik. Yes, the Pulsar topic is a persistent one.