24.3.12 Pre-release

[Enmk]

Build/Testing/Packaging Improvement

• Enable building and testing on Altinity infrastructure (#413)

Bug fix

• Support executing function during assignment of parameterized view value (#63502 by @SmitaRKulkarni via #444)
• Fix serialization of parameterized view parameters (#67654 by @shiyer7474 via #502)
• fix intersect parts when restart after drop range (#63202 by @hanfei1991 via #495)

Improvement

• Support aliases in parametrized view function (#65190 via @kssenii #500)
• Ignore allow_suspicious_primary_key on ATTACH and verify on ALTER (#64202 by @azat via #494)
• Thread pool metrics (#68674 by @filimonov via #503)
• more advanced SSL options for Keeper (#69582 by @antonio2368 via #496)
• Add fault injection for "Cannot allocate thread" (#62266 by @tavplubix via #508)
• Support S3 access through AWS Private Link Interface endpoints. (#62208 by @arthurpassos via #498)
• Set input_format_parquet_filter_push_down default value to false #511

Build/Testing/Packaging Improvement

• ubuntu:22.04 as a base image for clickhouse-server docker image #497
• alpine:3.20.3 as clickhouse-keeper base image to (lowest number of CVEs) #517

[altinity-robot]

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

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

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
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	⏳ 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
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	❌ failure

Successful checks

Check name	Description	Status
Compatibility check	Checks that clickhouse binary runs on distributions with old libc versions. If it fails, ask a maintainer for help	✅ success
Docker keeper image	The check to build and optionally push the mentioned image to docker hub	✅ success
Docker server image	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
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