Allow users to specify a custom range for the range filter when using parallel replicas with dynamic shards

[josh-hildred]

Allow users to specify a custom range for the range filter when using parallel replicas with dynamic shards. This change is particular useful when the custom key expression involves the primary key and relevant values of the primary key are known to be uniformly distributed over some range. For example, if a query is of the form WHERE k >= k1 and k <= k2 and has parallel_replicas_custom_key = 'k' with parallel_replicas_custom_key_filter_type = 'range' by setting parallel_replicas_custom_key_range_lower=k1 and parallel_replicas_custom_key_range_upper=k2, we are able to better parallelize this query over the replicas. This is because when an upper bound k1 and lower bound k2 are provided, we can split processing based on the range [k1, k2] rather than [0, INT_MAX] (I.E the custom key only needs to be uniformly distributed over the range [k1, k2] rather than on [0, INT_MAX]). Furthermore, if k is the primary key we also get better primary index usage leading to less "double loading" data at replicas.

Note: This setting will not cause any additional data to be filtered during query processing, rather it changes the points at which the range filter breaks up the range [0, INT_MAX] when parallelizing the query.

Changelog category (leave one):

• Improvement

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Add settings parallel_replicas_custom_key_range_lower and parallel_replicas_custom_key_range_upper to control how parallel replicas with dynamic shards parallelizes queries when using a range filter.

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings

NOTE: If your merge the PR with modified CI you MUST KNOW what you are doing
NOTE: Checked options will be applied if set before CI RunConfig/PrepareRunConfig step

• Allow: Integration Tests
• Allow: Stateless tests
• Allow: Stateful tests
• Allow: Unit tests
• Allow: Performance tests
• Allow: All with aarch64
• Allow: All with ASAN
• Allow: All with TSAN
• Allow: All with Analyzer
• Allow: All with Azure
• Allow: Add your option here

---

• Exclude: Fast test
• Exclude: Integration Tests
• Exclude: Stateless tests
• Exclude: Stateful tests
• Exclude: Performance tests
• Exclude: All with ASAN
• Exclude: All with TSAN
• Exclude: All with MSAN
• Exclude: All with UBSAN
• Exclude: All with Coverage
• Exclude: All with Aarch64

---

• do not test (only style check)
• disable merge-commit (no merge from master before tests)
• disable CI cache (job reuse)
• allow: batch 1 for multi-batch jobs
• allow: batch 2
• allow: batch 3
• allow: batch 4, 5 and 6

[robot-ch-test-poll3]

This is an automated comment for commit 2129401 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	❌ failure
Performance Comparison	Measure changes in query performance. The performance test report is described in detail here. In square brackets are the optional part/total tests	❌ 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
A Sync	If it fails, ask a maintainer for help	✅ success
AST fuzzer	Runs randomly generated queries to catch program errors. The build type is optionally given in parenthesis. If it fails, ask a maintainer for help	✅ success
ClickBench	Runs [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table	✅ success
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 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
Docs check	Builds and tests the documentation	✅ success
Fast test	Normally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here	✅ success
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	✅ success
Install packages	Checks that the built packages are installable in a clear environment	✅ success
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	✅ success
Mergeable Check	Checks if all other necessary checks are successful	✅ success
PR Check	Checks correctness of the PR's body	✅ success
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Style check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	✅ success
Unit tests	Runs the unit tests for different release types	✅ success
Upgrade check	Runs stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts	✅ success

[josh-hildred]

Thank you for working with me on this one @antonio2368!

[antonio2368]

@josh-hildred thanks for the contribution, please continue pushing good PRs 🙂