Clickhouse-connect

Latest version: v0.7.12

Safety actively analyzes 638755 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 12 of 16

0.4.6

Bug Fixes
* Fixed a major settings issue with connecting to a readonly database (introduced in v0.4.4)
* Fix for broken database setup dialog with recent Superset versions using SQLAlchemy 1.4

0.4.5

Bug Fixes
* Common settings were stored in an immutable named tuple and could not be changed. This is fixed.
* Fixed issue where the query_arrow method would not use the client database

0.4.4

Bug Fixes
* Ignore all "transport settings" when validating settings. This should fix https://github.com/ClickHouse/clickhouse-connect/issues/80
for older ClickHouse versions

0.4.3

New Features
* The get_client method now accepts a http_adapter parameter to allow sharing a requests.HTTPAdapter (and its associated
connection pool) across multiple clients.
* The VERSION file is now included in every package installation. Closes https://github.com/ClickHouse/clickhouse-connect/issues/76

0.4.2

New Features
* Global/common configuration options are now available in the `clickhouse_connect.common` module. The available settings are:
* `autogenerate_session_id` [bool] Whether to generate a UUID1 session id used for every client request. Defaults to True. Disabling this can facilitate client sharing and load balancing in some use cases.
* `dict_parameter_format` [str] Options are 'json' and 'map'. This controls whether parameterized queries convert a Python dictionary to JSON or ClickHouse Map syntax. Default to `json` for insert into Object('json') columns.
* `invalid_setting_action` [str] Options are 'send' and 'drop'. Client Connect normally validates and drops (with a warning any settings that aren't recognized by the Server or are readonly).
Changing this setting to 'send' will include such settings with the request anyway -- which will normally result in an error being returned.
* The `clickhouse_connect.get_client` method now accepts a `settings` dictionary argument for consistency with other client methods.

Bug Fixes
* Fixed insert of Pandas Dataframes for Timestamp columns with timezones https://github.com/ClickHouse/clickhouse-connect/issues/77
* Fixed exception when inserting a Pandas Dataframes with NaType values into ClickHouse Float column (see known issue)

Known Issue
When inserting Pandas DataFrame values into a ClickHouse `Nullable(Float*)` column, a Float NaN value will be converted to a ClickHouse NULL.
This is a side effect of a Pandas issue where `df.replace` cannot distinguish between NaT and NaN values: https://github.com/pandas-dev/pandas/issues/29024

0.4.1

Bug Fixes
* Numpy array read and write compatibility has been refined and performance has been improved. This fixes https://github.com/ClickHouse/clickhouse-connect/issues/69
* Pandas Timestamp objects are now correctly handled for all supported ClickHouse Date* types. This fixes https://github.com/ClickHouse/clickhouse-connect/issues/68
* SQLAlchemy datatypes are now correctly mapped to the underlying ClickHouse type regardless of case. This fixes an issue with migrating Superset datasets and queries from
clickhouse-sqlalchemy to clickhouse-connect. Thanks to [Eugene Torap](https://github.com/EugeneTorap)

Page 12 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.