adding mysql-connector-python to the list of pip packages inside venv-mysql

Question

adding mysql-connector-python to the list of pip packages inside venv-mysql

justmike1 opened this issue a year ago · comments

Hey,

I am using datahub-actions to ingest my MySQL and I have noticed you guys are using pymysql as the default connector for mysql integration, this is causing problems regarding connectivity and ssl, the fix was to use the feature:

sqlalchemy_uri: mysql+mysqlconnector://user:password@x.x.x.x:3306/smth_data

and to exec to the datahub-actions pod, activate the venv-mysql, and to manually install the package:

mysql-connector-python 8.1.0

github-actions · Answer 1 · Sun Sep 03 2023 09:46:58 GMT+0800 (China Standard Time)

This issue is stale because it has been open for 30 days with no activity. If you believe this is still an issue on the latest DataHub release please leave a comment with the version that you tested it with. If this is a question/discussion please head to https://slack.datahubproject.io. For feature requests please use https://feature-requests.datahubproject.io

github-actions · Answer 2 · Wed Oct 04 2023 09:47:10 GMT+0800 (China Standard Time)

This issue was closed because it has been inactive for 30 days since being marked as stale.

Harshal Sheth · Answer 3 · Wed Oct 04 2023 09:58:57 GMT+0800 (China Standard Time)

@justmike1 I missed this one. I don't think it makes sense for mysql to require both connector types, but we could do something similar to what we've done for mssql and mssql-odbc to have two possible dependency sets for the same connector.