forked from ClickHouse/ClickHouse
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
22.3.15 Pre-release PR #208
Merged
Merged
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 `v22.3.x.y-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 etc.
Support `batch_delete` capability for GCS
…bjects Fixes for objects removal in `S3ObjectStorage`
Starting a release from release_branches.yml Fixed error in build_report_check.py
Window functions and GCP fixes ClickHouse#36944, ClickHouse#34632, ClickHouse#37659 and ClickHouse#37882
Preparing for a release
Reverted VERSION_REVISION to value that was there before changes from Altinity's size Added VERSION_TWEAK, VERSION_FLAVOUR with proper values Utilizing tweak and flavour in version from autogenerated_versions.txt
Proper version with proper VERSION_REVISION
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 `v22.3.x.y-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 etc.
Starting a release from release_branches.yml Fixed error in build_report_check.py
Window functions and GCP fixes ClickHouse#36944, ClickHouse#34632, ClickHouse#37659 and ClickHouse#37882
Support `batch_delete` capability for GCS
Preparing for a release
…bjects Fixes for objects removal in `S3ObjectStorage`
Reverted VERSION_REVISION to value that was there before changes from Altinity's size Added VERSION_TWEAK, VERSION_FLAVOUR with proper values Utilizing tweak and flavour in version from autogenerated_versions.txt
Proper version with proper VERSION_REVISION
…`ExpressionAnalyzer`, shall be `aggregated_columns`.
…ast value in window.
…tants" This reverts commit a020fe3, reversing changes made to 8c06abe. Reverted to fix ClickHouse#37812 missing columns in case of using constants in CTE
…`ExpressionAnalyzer`, shall be `aggregated_columns`.
…ast value in window.
By cherry-picking a8d8293: Fix unused columns introduced by with stmt
…nked-array-deserialization Add support for extended (chunked) arrays for Parquet format
Backport ClickHouse#40732 to 22.3: Fix memory leak while pushing to MVs w/o query context (from Kafka/...)
Enmk
force-pushed
the
releases/22.3.15
branch
from
December 7, 2022 11:17
85954ac
to
4ef30f2
Compare
…n_dictionary_to_ch_lc Fix arrow column dictionary to ch lc
Backport ClickHouse#43297 to 22.3
…column_parsing Flatten list type arrow chunks on parsing
Backport ClickHouse#43297 to 22.3
(cherry picked from commit 120dc30)
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 Community Build v22.3.15.33-lts
Bug fixes
S3ObjectStorage
ClickHouse/ClickHouse#37882 by @excitoon (via Window functions and GCP fixes ClickHouse/ClickHouse#36944, ClickHouse/ClickHouse#34632, ClickHouse/ClickHouse#37659 and ClickHouse/ClickHouse#37882 #164)Unknown identifier (aggregate-function)
exception which appears when a user tries to calculate WINDOW ORDER BY/PARTITION BY expressions over aggregate functions ClickHouse/ClickHouse#39762 by @quickhouse (via FixedUnknown identifier (aggregate-function)
exception which appears when a user tries to calculate WINDOW ORDER BY/PARTITION BY expressions over aggregate functions — backport of ClickHouse/ClickHouse#39762 #189)Improvements
batch_delete
capability for GCS ClickHouse/ClickHouse#37659 by @frew (via Window functions and GCP fixes ClickHouse/ClickHouse#36944, ClickHouse/ClickHouse#34632, ClickHouse/ClickHouse#37659 and ClickHouse/ClickHouse#37882 #164)