Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Unintended behavior
View staffing
Description
The customer is using “/” in a BQ query as an alias for a field name, which is not a valid supported character to be used as the field name, alias [0.0]. The issue is that the query job fails with an inappropriate/meaningless error [1] in certain situations.
More explanations:
The BigQuery (BQ) job having the non supported character “/” (slash) in the field name alias and contains the CREATE OR REPLACE TABLE statement in it, it fails with the error [1]
“An internal error occurred and the request could not be completed”. Which does not meaningfully describe the root cause of the error.
However, while executing the same SELECT statement having only a few fields and without CREATE OR REPLACE TABLE statement (including the non supported character “/” (slash) in the field name alias), user receives the expected error message as the outcome. [2]
What you expected to happen:
- Show an appropriate error message that help troubleshoot the issue
Steps to reproduce:
a) Query has the CREATE OR REPLACE TABLE statement in it produces the error [1]
b) Query has the SELECT statement produces the error [2]
References:
[0]
[1] 'An internal error occurred and the request could not be completed. This is usually caused by a transient issue. Retrying the job with back-off as described in the BigQuery SLA should solve the problem:
[2] "Invalid field name "event_params_class rank/class size". Fields must contain the allowed characters, and be at most 300 characters long. For allowed characters, please refer to