New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metabase v0.34 does not display date, datetime fields from AWS Athena. #11607
Comments
Hi @kiansiong It seems like parts of the Diagnostic Info is missing, can you copy it again? Admin > Troubleshooting. Have you considered creating an issue on https://github.com/dacort/metabase-athena-driver since the problem is specific to the driver, not general about Metabase? Besides the very old Java version, I don't know, but there are very few details. So you don't see any warnings/errors in the log or browser console? |
hi @flamber , thanks for the quick response.
|
Just for reference, looks like similar thing is happening with Oracle driver too: |
I'm tracking this bug over on dacort/metabase-athena-driver#27 - the tl;dr is that the Athena JDBC driver doesn't support some of the new |
This is an upstream issue with the 3rd-party Athena driver (needs to be updated) but it should be an easy fix, there's shared implementation code to work around drivers with no Java 8 support already in place. I added notes about how to use that in the issue linked above |
Describe the bug
All date and datetime fields are not being displayed. Underlying database is AWS Athena.
Data is retrieved from database correctly, evident by casting the date field to string using date_format(). However, any field with data type = date / datetime is not displayed / render on screen.
Logs
Please include javascript console and server logs around the time this bug occurred. For information about how to get these, consult our bug troubleshooting guide
To Reproduce
Select any fields with datatype = date / datetime, with database AWS Athena.
Expected behavior
Date / Datetime fields should be displayed.
Screenshots
Information about your Metabase Installation:
You can get this information by going to Admin -> Troubleshooting.
{
"browser-info": {
"language": "en-US",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.88 Safari/537.36",
"vendor": "Google Inc."
},
"system-info": {
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "1.8.0_111-internal-alpine-r0-b14",
"java.vendor": "Oracle Corporation",
"java.vendor.url": "http://java.oracle.com/",
"java.version": "1.8.0_111-internal",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "25.111-b14",
"os.name": "Linux",
"os.version": "4.9.0-7-amd64",
"user.language": "en",
"user.timezone": "GMT"
},
"metabase-info": {
"databases": [
"athena"
],
"hosting-env": "unknown",
"application-database": "mysql",
"run-mode": "prod",
"version": {
"tag": "v0.34.0",
"date": "2019-12-19",
"branch": "release-0.34.x",
Severity
Severity High. This is affecting all datetime fields globally. Which limits any time series visualisations being displayed in Metabase.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: