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
Describe the bug
I get failures, see below, with the MySQL source after updating to Datahub v0.9.2 from v0.8.43. I get these failures where the database name has upper case characters. The name of the database where I get the failure below is really amhDb. I suspect that error was introduced when introducing TwoTierSQLAlchemySource in the MySQLSource.
'failures': {'amhdb': ['Tables error: (pymysql.err.OperationalError) (1049, "Unknown database \'amhdb\'")\n[SQL: SHOW FULL TABLES FROM `amhdb`]\n(Background on this error at: https://sqlalche.me/e/14/e3q8)']},
To Reproduce
Ingest data with the mysql source where the database name has uppercase characters in the name.
Expected behavior
I do not expect any failure like in v0.8.43 when the database has a name with uppercase characters.
Desktop (please complete the following information):
Datahub version v0.9.2
Additional context
I suspect (I have not verified this) that the databases from inspector.get_schema_names() on line 84 are all in lower case and then when the new url is created on line 87 is defined with the name all in lower case and the error is introduced and I get failures when the inspector is used.
Describe the bug
I get failures, see below, with the MySQL source after updating to Datahub v0.9.2 from v0.8.43. I get these failures where the database name has upper case characters. The name of the database where I get the failure below is really
amhDb
. I suspect that error was introduced when introducingTwoTierSQLAlchemySource
in theMySQLSource
.To Reproduce
Ingest data with the mysql source where the database name has uppercase characters in the name.
Expected behavior
I do not expect any failure like in v0.8.43 when the database has a name with uppercase characters.
Desktop (please complete the following information):
Additional context
I suspect (I have not verified this) that the databases from
inspector.get_schema_names()
on line 84 are all in lower case and then when the newurl
is created on line 87 is defined with the name all in lower case and the error is introduced and I get failures when the inspector is used.datahub/metadata-ingestion/src/datahub/ingestion/source/sql/two_tier_sql_source.py
Lines 81 to 91 in feb9d59
The text was updated successfully, but these errors were encountered: