issue: GCP project IDs are randomly generated. However, sometimes GCP creates project IDs with words that are also SQL keywords, such INNER or UNION. It might not be common, but I have seen it happen a couple of times.
when:
MLOps Week
interface > main.py
Change:
query codes on main.py file should change from:
query = f"""
SELECT {",".join(COLUMN_NAMES_RAW)}
FROM {GCP_PROJECT_WAGON}.{BQ_DATASET}.raw_{DATA_SIZE}
WHERE pickup_datetime BETWEEN '{min_date}' AND '{max_date}'
ORDER BY pickup_datetime
"""
to
query = f"""
SELECT {",".join(COLUMN_NAMES_RAW)}
FROM `{GCP_PROJECT_WAGON}.{BQ_DATASET}.raw_{DATA_SIZE}`
WHERE pickup_datetime BETWEEN '{min_date}' AND '{max_date}'
ORDER BY pickup_datetime
"""
Just by wrapping the FROM statement with and solves the issue.
issue: GCP project IDs are randomly generated. However, sometimes GCP creates project IDs with words that are also SQL keywords, such INNER or UNION. It might not be common, but I have seen it happen a couple of times.
when: MLOps Week interface > main.py
Change: query codes on
main.py
file should change from:to
Just by wrapping the FROM statement with
and
solves the issue.