Backport #12121 to 20.5: Fix version column in replicated version collapsing merge tree#12392
Merged
Backport #12121 to 20.5: Fix version column in replicated version collapsing merge tree#12392
Conversation
…unused_shards This will avoid supperior log message in case of *optimize_skip_unused_shards_nesting already disables it. And also it is logical.
Possible approach for fixing #10574 The problem is that prepared sets are built correctly, it is a hash map of key -> set where key is a hash of AST and list of data types (when we a list of tuples of literals). However, when the key is built from the index to try and find if there exists a prepared set that would match it looks for data types of the primary key (see how data_types is populated) because the primary key has only one field (v in my example) it can not find the prepared set. The patch looks for any prepared indexes where data types match for the subset of fields found in primary key, we are not interested in other fields anyway for the purpose of primary key pruning.
Remove a note about read limits applied on threads level.
Tiny fixes for distributed queries
perf test: report queries with new functions separately
* asiana21-DOCSUP-925-max_parser_depth (#132) * docs(max_parser_depth): added the setting description * docs(max_parser_depth): some changes * Update docs/en/operations/settings/settings.md Co-authored-by: BayoNet <[email protected]> * Update docs/en/operations/settings/settings.md Co-authored-by: BayoNet <[email protected]> * Update docs/en/operations/settings/settings.md Co-authored-by: BayoNet <[email protected]> * docs(max_parser_depth): added ru translation * docs(max_parser_depth): removed quotation marks Co-authored-by: asiana21 <[email protected]> Co-authored-by: BayoNet <[email protected]> * CLICKHOUSEDOCS-522: Fixed the link. Co-authored-by: AsiaKorushkina <[email protected]> Co-authored-by: asiana21 <[email protected]> Co-authored-by: Sergei Shtykov <[email protected]>
Fix limiting the number of threads for VIEW.
Enable CodeQL security scanner
Dockerfile security check for `clickhouse-server`
Improve REVOKE command
…threads max_rows_to_read remove note about 'applied on each thread separately'
Test for input_format_allow_errors_num in CSV
…column ISSUES-4006 support first for ALTER ADD|MODIFY COLUMN
…a4a104bd6c3e0eb999dee84d229
…89a4a104bd6c3e0eb999dee84d229 Cherry pick #12121 to 20.5: Fix version column in replicated version collapsing merge tree
robot-clickhouse
added
the
pr-backport
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
15 participants
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.
Original pull-request #12121
Cherry-pick pull-request #12215
This pull-request is a last step of an automated backporting.
Treat it as a standard pull-request: look at the checks and resolve conflicts.
Merge it only if you intend to backport changes to the target branch, otherwise just close it.