Clickhouse-connect

Latest version: v0.7.14

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

Scan your dependencies

Page 6 of 16

0.6.9

Improvements
- Logging and exception handling for failed insert transformations has been reworked. If an exception is thrown when attempting to
convert Python, Pandas, or Numpy data into ClickHouse Native format, the column name and type will be logged, as well as a
stack trace of actual exception (note this may be in the C/Cython code, so the exception data may still be difficult to interpret).
This partially addresses https://github.com/ClickHouse/clickhouse-connect/issues/229. Unfortunately determining data errors on a row level in
addition to the column level is not practical in most cases without seriously impacting performance.
- Version information has been moved from a top level `VERSION` to a Python `__version__` file in the package. This removes the Python 3.7 dependency
on importlib_metadata.
- Cython `.pyx`, and `.pxd` files are now included in the PyPI source distribution to improve compatibility with 3rd party build tools.

0.6.8

Bug Fix
- Fixed client `raw_insert` method when a compression method specified. https://github.com/ClickHouse/clickhouse-connect/issues/223

Improvement
- Add compression parameter to the clickhouse `tools.insert_file` method. '.gz' and '.gzip' extensions are automatically
recognized.

0.6.7

Bug Fixes
- Fixed an issue for older versions of ClickHouse where the server would send an initial block of 0 rows for larger queries.
This would break some queries with LowCardinality columns. Closes https://github.com/ClickHouse/clickhouse-connect/issues/221
- Fixed the`compression` alias for the `compress` client setting in SQLAlchemy/Superset DSN urls.

Improvements
- Upgraded to Cython 3.0.0 final release!
- Reversed the internal variable names of keys and indexes for low cardinality columns to be consistent with the ClickHouse server nomenclature.

0.6.6

Bug Fix
- Inserting into an Enum column from a Pandas DataFrame with integer values only inserted 0 values. This is fixed.
https://github.com/ClickHouse/clickhouse-connect/issues/219

0.6.5

Bug Fixes
- The Client min_version method now ignores unrecognized "text" elements. This could cause issues for unofficial
ClickHouse releases. Thanks to [Diego Nieto](https://github.com/lesandie) for the fix!
- In most cases insert query is now sent as part of the POST body instead of as a query parameter. This fixes
https://github.com/ClickHouse/clickhouse-connect/issues/213. Note that this does not happen for direct file inserts
using the `driver.tools` module, since these rely on an unmodified buffered input stream to efficiently upload files.
In that case the actual insert query will still be passed as a query parameter.
- All datetime objects returned from a query will now be timezone aware. This fixes https://github.com/ClickHouse/clickhouse-connect/issues/210.
There remains one exception to this -- if the calculated timezone and the local timezone are both UTC, then naive timezones
will be used to improve performance in such "all UTC" environments.
- Inserting Python dictionaries into a ClickHouse "named" Tuple column now works correctly. Fixes https://github.com/ClickHouse/clickhouse-connect/issues/215.
Note that using dictionaries for inserts will be noticeably slower than inserting the equivalent Python tuple value
(with elements in the correct order)

Improvements
- Client error messages used to be cut off at 240 characters to avoid creating huge log files. This value is now
configurable using the `common.max_error_size` setting. Use `0` for this setting to get the full ClickHouse
error message. In addition, the default has been changed to `1024` to capture more SQL errors without needing to
modify the global setting value. Thanks to [Ramlah Aziz](https://github.com/RamlahAziz) for the update!
- All Client insert methods now return a simple QuerySummary object, which includes properties `written_rows`,
`written_bytes`, and `query_id` calculated from ClickHouse HTTP response headers. A QuerySummary object is also
returned from the Client `command` method if the command does not return other data. Closes https://github.com/ClickHouse/clickhouse-connect/issues/216
- Version determination no longer indirectly depends on the setuptools `pkg_resources` package. This also
avoids some indirect dependency problems. Thanks to [cwegener](https://github.com/cwegener) for the PR!

0.6.4

Bug Fixes
- Quote database name when retrieving tables via SQLAlchemy. Fixes the Superset issue https://github.com/apache/superset/issues/24372
for recent versions of Superset using clickhouse-connect
- Don't rely on the ClickHouse currentDatabase() function to set an explicit database parameter. This should not change functionality
when no database is specified in Client creation since ClickHouse will use the user's default database in that situation regardless.
Fixes https://github.com/ClickHouse/clickhouse-connect/issues/207

Page 6 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.