Releases: ClickHouse/metabase-clickhouse-driver
Releases · ClickHouse/metabase-clickhouse-driver
1.51.0
1.50.7
1.50.6
1.50.5
1.50.4
1.50.3
Improvements
- The driver no longer explicitly sets
allow_experimental_analyzer=0
settings on the connection level; the new ClickHouse analyzer is now enabled by default.
1.50.2
1.50.1
New features
- Enabled
:set-timezone
(docs) Metabase feature in the driver. (#200) - Enabled
:convert-timezone
(docs) Metabase feature in the driver. (#254)
Other
- The driver now uses
session_timezone
ClickHouse setting. This is necessary to support the:set-timezone
and:convert-timezone
features; however, this setting was introduced in 23.6, which makes it the minimal required ClickHouse version to work with the driver.
1.50.0
After Metabase 0.50.0, a new naming convention exists for the driver's releases. The new one is intended to reflect the Metabase version the driver is supposed to run on. For example, the driver version 1.50.0 means that it should be used with Metabase v0.50.x or Metabase EE 1.50.x only, and it is not guaranteed that this particular version of the driver can work with the previous or the following versions of Metabase.
New features
- Added Metabase 0.50.x support.
Improvements
- Bumped the JDBC driver to 0.6.1.
Bug fixes
- Fixed the issue where the connection impersonation feature support could be incorrectly reported as disabled.
Other
- The new ClickHouse analyzer, which is enabled by default in 24.3+, is disabled for the queries executed by the driver, as it shows some compatibilities with the queries generated by Metabase (see this issue for more details).
- The
:window-functions/offset
Metabase feature is currently disabled, as the default implementation generates queries incompatible with ClickHouse. See this issue for tracking.
1.5.1
Requires at least Metabase 0.49.14 or any patch version after that.
Bug fixes
- Fixed the issue where the Metabase instance could end up broken if the ClickHouse instance was stopped during the upgrade to 1.5.0. (#242)
- Fixed variables substitution with Nullable Date, Date32, DateTime, and DateTime64 columns, where the generated query could fail with NULL values in the database due to an incorrect cast call. (#243)