:connection-impersonation does not work well with clustered setups and is disabled for now, at least until we find a proper way to enforce session-level settings within clusters. Related to #192
Remove unnecessary CAST as timestamp calls - related to #127
For example, now toStartOfHour and similar functions will not be forced to call CAST:
SELECT
` toStartOfHour ` (` default `.` wares `.` createdAt `) AS ` createdAt `,
COUNT(*) AS ` count `
FROM
` default `.` wares `
WHERE
` default `.` wares `.` createdAt ` < ` parseDateTimeBestEffort ` ('2023-09-28 00:00:00.000Z')
GROUP BY
` toStartOfHour ` (` default `.` wares `.` createdAt `)
ORDER BY
` toStartOfHour ` (` default `.` wares `.` createdAt `) ASC
NB1: parseDateTimeBestEffort here still relies on the server timezone.
NB2: odd backtick spacing is due to a bug in Metabase itself.
Removed forward slash from serialized IPv4/IPv6. Resolves #190
NB: IPv4/IPv6 columns are temporarily resolved as type/TextLike instead of type/IPAddress base type due to an unexpected result in Metabase 0.47 type check, which leads to crashes in specific queries (at least in the tests). It was fixed on the main branch, but it is not part of any 0.47.x released yet.
Move introspection code out of the main file
Temporal bucketing with column-level timezones tests - currently it works a bit weird but, at the same time, correct enough for the UI display purposes.
Bump versions
Checklist
[x] Unit and integration tests covering the common scenarios were added - probably need to add some timezone-specific tests that won't pass on the previous version.
[x] A human-readable description of the changes was provided to include in CHANGELOG
:connection-impersonation
does not work well with clustered setups and is disabled for now, at least until we find a proper way to enforce session-level settings within clusters. Related to #192For example, now
toStartOfHour
and similar functions will not be forced to call CAST:NB1:
parseDateTimeBestEffort
here still relies on the server timezone. NB2: odd backtick spacing is due to a bug in Metabase itself.NB: IPv4/IPv6 columns are temporarily resolved as
type/TextLike
instead oftype/IPAddress
base type due to an unexpected result in Metabase 0.47 type check, which leads to crashes in specific queries (at least in the tests). It was fixed on the main branch, but it is not part of any 0.47.x released yet.Checklist