-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
generate-table-partitions
fails for Spanner with Unknown dialect spanner
#1059
Comments
Hi, The problem occurs because the Spanner backend behaves differently from the BigQuery backend - perhaps the Spanner backend is not fully implemented. I can work around this issue - however it might be a very simple fix in the Spanner backend. Here is a Python interpreter session demonstrating the issue. BigQuery works fine with the
The issue seems to be that the dialect Thanks. Sundar Mudupalli |
The easiest way to do this is to pass in the BQ dialect for Spanner clients in the This is a separate issue, but Spanner doesn't support ROW_NUMBER() as shown in this error when Spanner is the source system: Error: |
Hi
A typical
generate-table-partitions
command fails because we are not able to convert the IBIS where clause (i.e. an IBIS table expression) into SQL text. This works for 8 other databases BigQuery, Hive, MySQL, Oracle, Postgres, Snowflake, SQL Server and Teradata (we have test cases for all those databases).The command is
Replacing
my_spanner
(which points to a Spanner database) withmy_mysql
- i.e. validate against same database succeeds.The specific error is below:
The text was updated successfully, but these errors were encountered: