Hello guys,
first, let me thank you for putting so much effort into Metabase!
Now, in production I'm using v0.34, we started another instance with Metabase upgraded to v0.42.4 as a test with production config. All questions and dashboards are working except questions where I'm using GROUP BY HOUR. If I switch to DAY on interactive filter, it works.
So I converted question to SQL:
SELECT
trunc("SY_TEVRON"."TIMERRESULTS"."SCRIPTSTARTTIME", 'dd') AS "SCRIPTSTARTTIME",
avg("SY_TEVRON"."TIMERRESULTS"."TEST_DUR") AS "avg"
FROM "SY_TEVRON"."TIMERRESULTS"
WHERE ("SY_TEVRON"."TIMERRESULTS"."SCRIPTNAME" = 'TMWEB-B2B-BlokaceInternet'
AND "SY_TEVRON"."TIMERRESULTS"."TIMERNAME" = 'b2b_zvolitSpravuCisla'
AND "SY_TEVRON"."TIMERRESULTS"."TIMERSTATUS" = 'Pass')
GROUP BY trunc("SY_TEVRON"."TIMERRESULTS"."SCRIPTSTARTTIME", 'dd')
ORDER BY trunc("SY_TEVRON"."TIMERRESULTS"."SCRIPTSTARTTIME", 'dd') ASC
When I change in SQL dd to hh it works perfectly but I would love to make it working as a standard question.
Hi @ticka
Post "Diagnostic Info" from Admin > Troubleshooting.
And can you explain what the problem is? Are you seeing errors, if so post them. Perhaps screenshots would help understanding the problem better.
@ticka
So this problem is only happening on Oracle?
What is the actual database column type of the "Date" column? If it is DATE, then that's the problem. It should be DATETIME or TIMESTAMP.
Actually I cannot tell if it is oracle only or not. Hourly data is only in Oracle database. We have other data in MYSQL but these are only daily.
I will check with server admin about the version and ask him to upgrade if it is not v11. Good thing is, that old version is still running correctly with this database
we now have Java11 in place and still got the same error: Unsupported temporal bucketing: You can't bucket a :type/Date Field by :hour.
In Data model for this oracle DB, SCRIPTSTARTTIME is type of "Creation date". But the same value is set in old version which is working. I tried to set it to "Createion timestamp", discarder cache and rescan table but still, no success.