ClickHouse
ClickHouse copied to clipboard
Try to push down filter to both parts of join (on plan level).
Changelog category (leave one):
- Improvement
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
TODO
This is an automated comment for commit fb90c2e5daaa9ef128b083bb833189cb4783634e with description of existing statuses. It's updated for the latest CI running
❌ Click here to open a full report in a separate page
Successful checks
Check name | Description | Status |
---|---|---|
Docs check | Builds and tests the documentation | ✅ 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 |
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 |
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 | ❌ failure |
Mergeable Check | Checks if all other necessary checks are successful | ❌ failure |
Dear @KochetovNicolai, this PR hasn't been updated for a while. Will you continue working on it? If not, please close it. Otherwise, ignore this message.