23.3.13 Pre-release #310
Merged
23.3.13 Pre-release #310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
add comment and rename github robot token add clickhouse instance password parameter use Altinity's s3 bucket Use altinityinfra dockerhub images and minor adjustments (#135) Allow CI to be triggered on PR Proper error reporting during docker pull and lowercase version name allow `altinitystable` git tags Download specific MinIO version instead of latest - same as upstream master remove stale chmod More stable CI/CD builds: - Rebuilding all docker images - Reduced number of docker images - Rerunning functional tests even if those were already executed in previous run Added missing dependencies for stateful tests Re-generating _pb2 files on each test run Changed hardcoded docker images name prefixes from `clickhouse/` to `altinityinfra/` Pushing images as :latest too to avoid some test failures reverted back to use clickhouse/jdbc-bridge Fixed how version is generated: taking into account VERSION_TWEAK and VERSION_FLAVOUR Pushing checks events data to "gh-data" instead of "default" Using secrets for managing AWS access Fixed tag checking code to allow altinitystable version suffix Bumped Go version to get some CVE fixes Do not install clickhouse-diagnostics due to numerous CVEs in go runtime Removed unneeded docker images from list: codebrowser, sqlancer-test, keeper-jespen, keeper-jepsen-test, testflows-runner, fuzzer Using ccache instead of sccache Fixed ClickHouseVersion.get_version_from_string for some cases, fixed getting version flavour
Fix key condition on duplicate primary keys
…sary-sets Do not build sets for skip indexes if they are not used
23.3 Fix of DockerServerImages
…uild_skip_indices_if_not_used 23.3 backport of ClickHouse#48299 Do not build skip indices if not used
…condition_crash 23.3 backport of ClickHouse#48838 Fix crash with key condition on duplicate primary keys
Uploading src tgz and regression improvements
SignRelease cherrypick
23.3 port of #269 source upload
Changed order of jobs to make SignRelease start earlier than tests, and tests start after SignRelease
23.3 Port of #266 Signing binaries
…stomizations/23.3.5
…stomizations/23.3.8
…s_coredns_version 23.3 Backport of ClickHouse#53286 - Bring back **garbage** dns tests
…xpressions Disable "compile_expressions" setting by default
…lickHouse#50429) Previously it could create MergeTreeInOrder for each mark, however this could be very suboptimal, due to each MergeTreeInOrder has some memory overhead. Now, by collapsing all marks for one part together it is more memory effiecient. I've tried the query from the altinity wiki [1] and it decreases memory usage twice: SELECT * FROM repl_tbl FINAL WHERE key IN (SELECT toUInt32(number) FROM numbers(1000000) WHERE number % 50000 = 0) FORMAT Null - upstream: MemoryTracker: Peak memory usage (for query): 520.27 MiB. - patched: MemoryTracker: Peak memory usage (for query): 260.95 MiB. [1]: https://kb.altinity.com/engines/mergetree-table-engine-family/replacingmergetree/#multiple-keys And it could be not 2x and even more or less, it depends on the gaps in marks for reading (for example in my setup the memory usage increased a lot, from ~16GiB of RAM to >64GiB due to lots of marks and gaps). Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>
…compile_expressions 23.3 Backport of ClickHouse#51368 - Disable "compile_expressions" setting by default
other IPv6 addr, explicit 8.8.8.8 dns (cherry-picked a028c29)
…uet_array_inconsistent_offsets 23.3 Backport of ClickHouse#54370 - fix parquet array inconsistent offsets
…l-memory-usage 23.3 Backport of ClickHouse#50429 - Fix excessive memory usage for FINAL (due to too much streams usage)
Updating labels for on-demand runners
|
This is an automated comment for commit bac54d0 with description of existing statuses. It's updated for the latest CI running
|
…stomizations/23.3.13
Enmk
force-pushed
the
customizations/23.3.13
branch
from
cde9db7
to
a3b7bbb
Compare
Enmk
force-pushed
the
customizations/23.3.13
branch
from
b8d2485
to
8ca3201
Compare
This comment has been minimized.
This comment has been minimized.
…_data_skipping_index Fixed tests for queries/0_stateless/02780_final_streams_data_skipping…
Fix FINAL produces invalid read ranges in a rare case
…invalid_read_ranges Backport of ClickHouse#54934 Fix `FINAL` produces invalid read ranges in a rare case
23.3.13 ARM
…eload Fix reading from sparse columns after restart
…-columns-reload 23.3 Backport of ClickHouse#49660 - fix sparse columns reload
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes compared to upstream's v23.3.13.6-lts
Bug fixes
FINALproduces invalid read ranges in a rare case ClickHouse/ClickHouse#54934 by @nickitat via 23.3 Backport of #54934 FixFINALproduces invalid read ranges in a rare case #313)ratio_of_defaults_for_sparse_serializationback to1.0and restarting the server. (Fix reading from sparse columns after restart ClickHouse/ClickHouse#49660 by @CurtizJ via 23.3 Backport of #49660 - fix sparse columns reload #314)Performance improvement
Improvement
Build/Testing/Packaging Improvement
Upstream changes between v23.3.8.21-lts (1675f2264f3) and v23.3.13.6-lts (25635e27551)
Performance Improvement
ANYhash join if nothing is inserted. #48633 (vdimir).query_plan_optimize_primary_key = 1, query_plan_optimize_projection = 1. This fixes #48823 . This fixes #51173 . #52308 (Amos Bird).Build/Testing/Packaging Improvement
-ftime-trace) is uploaded to ClickHouse Cloud., the second attempt after #53100. #53213 (Alexey Milovidov).clickhouse startcommand. Fixes #51962. #53418 (Mikhail f. Shiryaev).Bug Fix (user-visible misbehavior in an official stable release)
countSubstrings()hang with empty needle and a column haystack #52409 (Sergei Trifonov).tuplewith one sparse column argument #52659 (Anton Popov).DelayedSource#53644 (Antonio Andelic).NOT FOR CHANGELOG / INSIGNIFICANT
02862_sorted_distinct_sparse_fix#53738 (Antonio Andelic).