23.8.8 Pre-release

[Enmk]

Bug fixes

• Fixes partition pruning for extra columns in a set. (Fix partition pruning of extra columns in set. ClickHouse/ClickHouse#55172 by @amosbird via 23.8 Backport of #55172 - Fix partition pruning of extra columns in set #342)
• Fixed rare bug when we produced invalid read ranges for queries with FINAL. Resulted in Cannot read out of marks range exception. (Fix FINAL produces invalid read ranges in a rare case ClickHouse/ClickHouse#54934 by @nickitat via 23.8 Backport of #54934 - Fix FINAL produces invalid read ranges in a rare case #343)
• Fix incorrect free space accounting for least_used JBOD policy (Fix incorrect free space accounting for least_used JBOD policy ClickHouse/ClickHouse#56030 by @azat via 23.8 Backport of #56030 - Fix incorrect free space accounting for least_used JBOD policy #344)
• Fix ALTER COLUMN with ALIAS that previously threw the NO_SUCH_COLUMN_IN_TABLE exception. (Backport #56493 to 23.8: Fix ALTER COLUMN with ALIAS ClickHouse/ClickHouse#57395 by @evillique via 23.8 Backport of #57395 - Fix ALTER COLUMN with ALIAS #345)
• Disable system.kafka_consumers by default (due to possible live memory leak) (Disable system.kafka_consumers by default (due to possible live memory leak) ClickHouse/ClickHouse#57822 by @azat via 23.8 Backport of #57822 - Disable system.kafka_consumers by default #346)

Performance improvements

• Fixed filtering by IN(...) condition for Merge table engine. (Fix key analysis (with set) for Merge engine ClickHouse/ClickHouse#54905 by @nickitat via 23.8 Backport of #54905 - Fix key analysis (with set) for Merge engine #341)

Build/Testing/Packaging Improvement

• Make builds possible on Altinity's infrastructure
• clickhouse-regression test suite (23.8.8 Regression #338 by @MyroTk)

[altinity-robot]

This is an automated comment for commit 193c1f9 with description of existing statuses. It's updated for the latest CI running

❌ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
ClickHouse build check	Builds ClickHouse in various configurations for use in further steps. You have to fix the builds that fail. Build logs often has enough information to fix the error, but you might have to reproduce the failure locally. The cmake options can be found in the build log, grepping for cmake. Use these options and follow the general build process	✅ success
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	✅ success
Docker image for servers	The check to build and optionally push the mentioned image to docker hub	✅ success
Install packages	Checks that the built packages are installable in a clear environment	✅ success
Push to Dockerhub	The check for building and pushing the CI related docker images to docker hub	✅ success
Ready for release	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success

Check name	Description	Status
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	⏳ pending
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	❌ failure
Mergeable Check	Checks if all other necessary checks are successful	❌ failure
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ failure