You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a compatibility issue between the Pulsar Python client library version 3.6.0 and Pulsar server version 4.0.2 when used in Databricks.
Observed Issue
Pulsar Client Library Version: 3.5.0
Environment: Databricks notebook
Problem: Unable to connect and create a client.
Error Details
When using Pulsar client library version 3.6.0 in Databricks, the following error is encountered:
0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [ERROR:__main__:Error connecting to Pulsar: Pulsar error: ConnectError 0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 ERROR [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [
Solution
Downgrading to Pulsar client library version 3.5.0 resolves the issue.
Current Pulsar Server Version: 4.0.2
The text was updated successfully, but these errors were encountered:
I also have ran the 3.6.0
Python client against standalone without issue. The issue being reported is only occuring within the Azure Databricks environment.
There is a compatibility issue between the Pulsar Python client library version 3.6.0 and Pulsar server version 4.0.2 when used in Databricks.
Observed Issue
Error Details
When using Pulsar client library version 3.6.0 in Databricks, the following error is encountered:
0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [ERROR:__main__:Error connecting to Pulsar: Pulsar error: ConnectError 0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 ERROR [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [0000-00-00 00:00:00.000 INFO [
Solution
Downgrading to Pulsar client library version 3.5.0 resolves the issue.
The text was updated successfully, but these errors were encountered: