We are using 2 engine, BigQuery and PostgreSQL. If the Engine is PostgreSQL, after we change Localization report timezone to UTC, the timezone is shown as expected. However if the Engine is BigQuery, we would face the difficulties as I described below.
-
When Engine is BigQuery
1a. The datetime columns in BigQuery looks like this. Theoriginal_created_atis the same ascreated_at_utc.
1b. However, in Metabase, when the timezone is either Asia/Jakarta or UTC it shows like this.
-
When Engine is PostgreSQL
2a. The datetime columns in BigQuery looks like this. Theoriginal_created_atis the same ascreated_at_utc.
2b. In Metabase, if timezone is UTC it shows like this (This is what we expect).
Metabase Diagnostic Info
{
"browser-info": {
"language": "en-GB",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "11.0.15+10",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "11.0.15",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "11.0.15+10",
"os.name": "Linux",
"os.version": "5.10.197+",
"user.language": "en",
"user.timezone": "Asia/Jakarta"
},
"metabase-info": {
"databases": [
"bigquery-cloud-sdk",
"postgres"
],
"hosting-env": "unknown",
"application-database": "postgres",
"application-database-details": {
"database": {
"name": "PostgreSQL",
"version": "14.9"
},
"jdbc-driver": {
"name": "PostgreSQL JDBC Driver",
"version": "42.3.2"
}
},
"run-mode": "prod",
"version": {
"date": "2022-06-27",
"tag": "v0.43.4",
"branch": "release-x.43.x",
"hash": "61cc28e"
},
"settings": {
"report-timezone": "Asia/Jakarta"
}
}
}
Could you please help investigate the reason behind it? We are using Google Cloud Kubernetes Engine to run our Metabase instance. Thanks for your help in advance.