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
I am encountering an issue with Apache Airflow 2.9.2 when attempting to test a connection to Kafka.
I followed the integration guide as per the documentation here.
After setting up the connection to Kafka, testing the connection with the command airflow connections test <connection-name> results in a failure.
It appears that the test utilizes KafkaBaseHook, and it fails when reaching this specific statement: base.py#L56
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Yes. There is a base Kafka connection and when "Test connection" is used, it instantiates Hook based on the type of connection - so it will instantiate the Base Kafka Hook and there _get_client is Not Implemented - easy fix will be to turn the NotImplemented into a client that can do a basic connection test.
Apache Airflow Provider(s)
apache-kafka
Versions of Apache Airflow Providers
1.4.1
Apache Airflow version
2.9.2
Operating System
Debian 11
Deployment
Docker-Compose
Deployment details
No response
What happened
I am encountering an issue with Apache Airflow 2.9.2 when attempting to test a connection to Kafka.
I followed the integration guide as per the documentation here.
After setting up the connection to Kafka, testing the connection with the command
airflow connections test <connection-name>
results in a failure.It appears that the test utilizes KafkaBaseHook, and it fails when reaching this specific statement: base.py#L56
Here is the configuration dictionary I am using
What you think should happen instead
I think it should use an instance of KafkaAdminClientHook instead of an instance of the generic class, which throws when invoking _get_client
How to reproduce
airflow connections test <connection-name>
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: