#31363 format template configure in settings

[Blargian]

Hi Clickhouse team,
I'm opening a PR for this feature. Look forward to your feedback and fixing any issues. :)

Changelog category (leave one):

• New Feature

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

The user can now specify the template string directly in the query using format_schema_rows_template as an alternative to format_template_row. Closes #31363.

Documentation entry for user-facing changes

• Documentation is written - English and Russian. (То что написал на русском скорее всего есть ошибки, я не носитель русского... нужно помощь исправить пж)

• docs/en/interfaces/formats.md

• docs/ru/interfaces/formats.md

• docs/en/operations/settings/settings-formats.md

Example usage not yet added, I can add that if needed.

[Felixoid]

Dear @Blargian, the # in the branch name breaks the CI because we don't URL-encode it. The fix won't be instant, so please recreate the PR from another branch without special symbols in the name.

[Felixoid]

Funny fact, the url in the GitHub API is malformed too https://api.github.com/repos/ClickHouse/ClickHouse/compare/ClickHouse%3Amaster...Blargian%3A%2331363_format_template_configure_in_settings

[Felixoid]

If the commit would help, I'll create independent PR

[robot-ch-test-poll2]

This is an automated comment for commit 42628fd 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
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
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	✅ 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. Integrational 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
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
SQLTest	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
SQLancer	Fuzzing tests that detect logical bugs with SQLancer tool	✅ success
Sqllogic	Run clickhouse on the sqllogic test set against sqlite and checks that all statements are passed	✅ 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

Check name	Description	Status
Stateful tests	Runs stateful functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ failure
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	❌ failure

[Felixoid]

I have restored the previous commit to not affect the autoapprove lambda. It should block changes into tests/ci directory

[Blargian]

@Felixoid thanks for the heads up and also for the fix! I notice the last commits I made didn't trigger the CI to start again. Do you maybe know why?

[Felixoid]

Do you maybe know why?

Do you know a joke?

-- We have good and bad news for you
-- I'd like to start with a good part, doctor
-- We'll call decease after you

#59184

Maybe we'll find another broken assumption in the CI code in the end of the day ¯\_(ツ)_/¯

[Blargian]

Do you know a joke?

-- We have good and bad news for you
-- I'd like to start with a good part, doctor
-- We'll call decease after you

Рад служить! )

[Blargian]

@Avogar the last few tests are all failing on issues related to not being able to find, or remove a .tmp version of my shell test. Where does the .tmp version come from, I guess it's something the tests generate? Is there a specific permission level that test files should be given?

[Avogar]

The problem is that you used filenames 00937_template_output_format_row.tmp/00937_template_output_format_resultset.tmp, the same as in test 00937_template_output_format.sh, but we run tests in parallel, so one test can create files, another remove them. Also in Stateless tests flaky check we run the same test in parallel with itself, so the same problem. Let's use unique filenames using env variable $CLICKHOUSE_TEST_UNIQUE_NAME

[Blargian]

@Avogar is there some bigger issue with CI at the moment? Fast tests fails since I updated my branch from master this morning. It was okay yesterday.

edit - related to #59453 which caused fast tests to fail

[Avogar]

Test 02720_row_policy_column_with_dots was broken in master by accident, already fixed, so should be ok now

[Blargian]

Tests still failing:

• test_storage_kafka/test.py::test_system_kafka_consumers_rebalance_mv (ThreadSanitizer data race in librdkafka (test_storage_kafka) #56043)
• 02981_vertical_merges_memory_usage (02981_vertical_merges_memory_usage flaky #59648)

[Avogar]

Sorry for waiting, I was on vacation. I will resolve conflicts and merge this PR when tests are finished

[Blargian]

Sorry for waiting, I was on vacation. I will resolve conflicts and merge this PR when tests are finished

No worries, thanks! Hope it was a good vacation 👍