This message was deleted.

Does Pulsar support message exchange between tenants?

This message was deleted.

This message was deleted.

This message was deleted.

Hi, I already have a running, working pulsar cluster, and trying to connect to it using AOP. I’ve downloaded the .nar file, and copied it to all the pulsar brokers to the path ./protocols. Accordingly, I’ve added the following configuration to the broker.conf file of each broker: messagingProtocols=amqp protocolHandlerDirectory=./protocols amqpListeners=amqp://127.0.0.1:5672 I restarted the brokers, and using netstat -tulpn | grep java, I can see that port 5672 is listening. I’ve created a namespace for a rabbitmq VHost using the following CLI command: pulsar-admin namespaces create -b 1 public/vhost1 Now I want to connect to the pulsar cluster using an AMQP client. I wrote the following code in Python using the rabbitmq pika library: import pika connection = pika.BlockingConnection(pika.ConnectionParameters(host=‘host1’, port=5672, virtual_host=‘vhost1’)) Running the code gives me the following error: pika.exceptions.IncompatibleProtocolError: StreamLostError: (‘Transport indicated EOF’,) Can anyone help me to figure out why this error occurs, and how to resolve it? Thanks!

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

https://github.com/apache/pulsar/discussions/20184 help help thank lot

https://github.com/streamnative/oxia 🤘👌

📣 HELP make Pulsar Metrics better 📣 Today I raised a PIP (Pulsar Improvement Proposal), PIP-264, to solve two major problems for users of Pulsar: • Monitoring brokers with large topic count • No fine-grained control for metrics exporting PIP-264, will be OpenTelemetry-based, and improve so many aspects of Pulsar Metrics. Just to name a few of its goals: • Allow monitoring Pulsar broker with very high topic count (10k - 1M), without paying the price of high cardinality, by providing a mechanism which aggregates topic-level metrics to an aggregation level called Topic Metric Group which the operator controls dynamically. • Allow dictating (filtering) which metrics will be exported, per any granularity level metrics: namespace, topic metric group, topic, consumer, producer, subscription. • Provide a rich typed interface to hook into Pulsar metrics system for Plugin authors • Make histogram reporting conformant with Prometheus when exported to Prometheus format • Provide ability in the future to correlated metrics with logs and traces, by sharing context • Support the most efficient observability protocol, OTLP. • Stop using delta reset, everywhere, including function metrics • All Pulsar metrics are properly named following a well-defined convention, adhering to OTel Semantic Conventions for instrument and attribute naming where possible This proposal both improve Pulsar observability immensely, with the cost of non backward compatible changes. I would really appreciate any time you can allocate to reading and providing feedback 🙏 https://github.com/apache/pulsar/issues/20197

This message was deleted.

This message was deleted.

This message was deleted.

Hi, all. We are thrilled to tell you that Pulsar 3.0.0 is finally announced! This is a huge milestone for Pulsar. For more information about Pulsar 3.0, please check out this blog post. We want to express our gratitude to everyone who contributed to making this release possible. Thank you!

This message was deleted.

This message was deleted.

This message was deleted.

Quick reminder about this very important PIP, which can really use some user/dev feedback

This message was deleted.

This message was deleted.

Hey everyone! If youre using the python client, do you know if its possible to subscribe to multiple schema-validated topcis? Take this example here, but imagine you had four topics with four different schemas: https://github.com/ta1meng/pulsar-python-avro-schema-examples/blob/main/example01_simple_schema/consumer_simple_schema.py

Does https://github.com/apache/pulsar-client-go/pull/805 work on shared subscription?