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 Oct 21, 2022. It is now read-only.
Describe the bug
Metabase 35.3 generates date range as the first ms from stardate and next period first ms.
IMHO time dimension and preaggregation rules are not applied properly.
Expected behavior
According to cubejs documentation ( updated to v 0.19.13) Metabase must follow the next rules:
Time dimension together with granularity constitute dimension. If date range isn't aligned with granularity common granularity is used. To match granularity date range should match it's start and end. For example for month it's ['2020-01-01T00:00:00.000', '2020-01-31T23:59:59.999'] and for day it's ['2020-01-01T00:00:00.000', '2020-01-01T23:59:59.999']. Date ranges are inclusive. Minimum granularity is second.
Version:
[v0.12.0]
The text was updated successfully, but these errors were encountered:
Describe the bug
Metabase 35.3 generates date range as the first ms from stardate and next period first ms.
IMHO time dimension and preaggregation rules are not applied properly.
{ "measures" : [ "Quotefacts.count" ], "dimensions" : [ "Quotefacts.salesrep" ], "timeDimensions" : [ { "dimension" : "Quotefacts.datequoted", "dateRange" : [ "2020-04-01T00:00:00+02:00", "2020-05-01T00:00:00+02:00" ] } ], "filters" : [ ], "order" : { "Quotefacts.count" : "desc", "Quotefacts.salesrep" : "asc" } }
Expected behavior
According to cubejs documentation ( updated to v 0.19.13) Metabase must follow the next rules:
Version:
[v0.12.0]
The text was updated successfully, but these errors were encountered: