pete
January 24, 2017, 3:43pm
#1
Several different #standardSQL queries generates errors:
for example:
'#standardSQL
select …
TIMESTAMP_TRUNC(ts_event , week) as week
(rest of query here which does work in BQ console)
generates an error :
3.17 - 3.35: Unrecognized function timestamp_trunc
Also, this type query:
'#standardSQL
with list as
(SELECT … (rest of valid standardSQL query here)
generates: Encountered " “WITH” "with “” at line 4, column 1. Was expecting:
sameer
January 24, 2017, 7:49pm
#2
yes, that’s a known issue, we’ll be fixing in the upcoming release
https://github.com/metabase/metabase/issues/3012 is the tracking issue
pete
February 19, 2017, 1:29pm
#3
whats the ETA for the fix, so that standardSQL is usable? Google is moving away from legacySQL, joins are much slower in legacySQL and so on. For our use case MetaBase is not usable if only supporting legacySQL