[source-mysql] 3.9.0-rc.25 doesn't import view table anymore

[oliviertassinari]

Connector Name

source-mysql

Connector Version

3.9.0-rc.25

What step the error happened?

During the sync

Relevant information

This logic is wrong:

airbyte/airbyte-integrations/connectors/source-mysql/src/main/kotlin/io/airbyte/integrations/source/mysql/MysqlSourceOperations.kt

Lines 222 to 224 in bec1c44

	val quickCount =
	"SELECT GREATEST(10, table_rows) FROM information_schema.tables WHERE table_schema = '$namespace' AND table_name = '$name'"
	val greatest = "GREATEST($greatestRate, $sampleSize / ($quickCount))"

SELECT GREATEST(null, 1);
-- returns `NULL`, MySQL v8.0.39-30.

Why does it happen? Because I'm syncing a view (TABLE_TYPE = VIEW), it's not a regular table:

So I believe #48035 is not correct.

Relevant log output

We used to sync all the records with:

https://cloud.airbyte.com/workspaces/9e090881-de2e-48c7-b268-2e86ad2525d9/connections/b46a92b8-8aa3-44e9-b17a-26067781a1cc/timeline

and now since https://cloud.airbyte.com/workspaces/9e090881-de2e-48c7-b268-2e86ad2525d9/connections/b46a92b8-8aa3-44e9-b17a-26067781a1cc/timeline

It syncs 0 records.

Contribute

• Yes, I want to contribute No, I already have my hands full with http://github.com/mui/material-ui.

[marcosmarxm]

Thank you for reporting the issue, @oliviertassinari. @xiaohansong and @rodireich, could someone have a look into this?

[rodireich]

Thanks I'm taking a look.

[rodireich]

[connection]
Another workspace with the same issue.
We rolled them back to legacy mysql until we get Views working

thanks @yardencarmeli

[oliviertassinari]

Another workspace with the same issue.

@rodireich It's the same workplace, actually.

We rolled them back to legacy mysql until we get Views working

Thanks, I couldn't find how to do it with the UI. Seems impossible, maybe another feature request?

Why was it upgraded to an unstable version in the first place (RC)? Could this be another bug? It looks like https://docs.airbyte.com/managing-airbyte/connector-updates#airbyte-cloud is not how it behaves in practice. Minor, patch, aren't applied, e.g. MySQL. Major aren't applied e.g. PostgreSQL or not correctly, e.g. MySQL. The self-hosting path looks better than current Cloud behavior. Even better would be https://www.getdbt.com/blog/introducing-release-tracks-for-dbt-version-upgrades.