ClickHouse
Add function printf for spark compatiability
Changelog category (leave one):
- New Feature
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Add function printf for spark compatiability
SELECT printf('%%%s %s %d', 'Hello', 'World', 2024)
Query id: 293631ab-3d21-4139-958d-715ce697da95
┌─printf('%%%s %s %d', 'Hello', 'World', 2024)─┐
1. │ %Hello World 2024 │
└──────────────────────────────────────────────┘
1 row in set. Elapsed: 0.002 sec.
This is an automated comment for commit 1103a2d669b9aadc55b381ec25cd8763a2bde8c2 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 |
|---|---|---|
| Stateless tests | Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc | ❌ failure |
Successful checks
| Check name | Description | Status |
|---|---|---|
| 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 |
| Builds | There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS | ✅ success |
| ClickBench | Runs [ClickBench](https://github.com/ClickHouse/ClickBench/) with instant-attach table | ✅ 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 |
| 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 | ✅ success |
| Stateful tests | Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc | ✅ success |
| Stress test | Runs stateless functional tests concurrently from several clients to detect concurrency-related errors | ✅ 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 |
@vdimir @den-crane it seems that almost all tests had passed, do you have any further reviews?
@taiyang-li @vdimir I've noticed this one doesn't support special characters. For example: select printf('%%s: %s', '\n\t'); returns \n\t
Is it expected, or is a bug?
@taiyang-li @vdimir I've noticed this one doesn't support special characters. For example:
select printf('%%s: %s', '\n\t');returns\n\tIs it expected, or is a bug?
Strange.. I can't reproduce it. I'm on x86 platform
SELECT printf('%%s: %s', '\n\t')
Query id: 0348d69c-d10d-4476-b6ca-c6a6d852d3ca
┌─printf('%%s: %s', '\n\t')─┐
1. │ %s:
│
└───────────────────────────┘