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
{{ message }}
This repository has been archived by the owner on Dec 11, 2022. It is now read-only.
I can't figure out how to write a query involving a subquery as it trys to interpret the from clause as a project
Expected Behavior
I can write a vaid biquery involve multiple from clauses
Actual Behavior
message:"Invalid project ID 'NNEST('$allusers''. Project IDs must contain 6-63 lowercase letters, digits, or dashes. Some project IDs also include domain name separated by a colon. IDs must start with a letter and may not end with a dash."
Steps to Reproduce the Problem
SELECT JSON_EXTRACT(jt, '$.email') as users from UNNEST('$allusers') as jt,
(i.e. It's a step towards the incredibly obvious - but really hard to do - thing of translating an id in a log to a meaningful name via a grafana variable. The query fragment isn't right yet but it should be enough of an example)
It may be better to have a project selector like in the builder rather than breaking the bigquery language by limiting what we can write?
Specifications
Version: 1.0.7
Platform:
Grafana Version: 7.3.5
The text was updated successfully, but these errors were encountered:
Bug Report
I can't figure out how to write a query involving a subquery as it trys to interpret the from clause as a project
Expected Behavior
I can write a vaid biquery involve multiple from clauses
Actual Behavior
message:"Invalid project ID 'NNEST('$allusers''. Project IDs must contain 6-63 lowercase letters, digits, or dashes. Some project IDs also include domain name separated by a colon. IDs must start with a letter and may not end with a dash."
Steps to Reproduce the Problem
(i.e. It's a step towards the incredibly obvious - but really hard to do - thing of translating an id in a log to a meaningful name via a grafana variable. The query fragment isn't right yet but it should be enough of an example)
It may be better to have a project selector like in the builder rather than breaking the bigquery language by limiting what we can write?
Specifications
The text was updated successfully, but these errors were encountered: