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
We have a model that is querying the BigQuery information schema. In contrast to regular tables living in datasets within projects, the INFORMATION_SCHEMA follows a different syntax that does not have to comply with the usual <project>.<dataset>.<table> format. E.g. this would be valid identifier for an information schema table:
myProject.`region-us`.INFORMATION_SCHEMA.TABLES`
We have a query like the following:
SELECT *
FROM `region-eu`.INFORMATION_SCHEMA.JOBS
When running sqlmesh create_external_models, we receive the following warning
We have a model that is querying the BigQuery information schema. In contrast to regular tables living in datasets within projects, the
INFORMATION_SCHEMA
follows a different syntax that does not have to comply with the usual<project>
.<dataset>
.<table>
format. E.g. this would be valid identifier for an information schema table:We have a query like the following:
When running
sqlmesh create_external_models
, we receive the following warningThe warning indicates that SQLMesh is interpreting
region-eu
as the project name, which is not true for information schema tables.The text was updated successfully, but these errors were encountered: