* for CSV and TSV input formats input_format_csv_enum_as_number,
input_format_tsv_enum_as_number settings should be enabled in order to
treat input value as enum id
The new setting should allow to control query complexity on leaf nodes
excluding the final merging stage on the root-node. For example, distributed
query that reads 1k rows from 5 shards will breach the `max_rows_to_read=5000`,
while effectively every shard reads only 1k rows. With setting `max_rows_to_read_leaf=1500`
this limit won't be reached and query will succeed since every shard reads
not more that ~1k rows.
Possible values:
- 1 - Do not merge aggregation states from different servers for distributed query processing - in case it is for certain that there are different keys on different shards.
- 2 - same as 1 but also apply ORDER BY and LIMIT stages
* Docs in English for the ttl_only_drop_parts setting.
* Docs in Russian.
* Update docs/ru/operations/settings/settings.md
Co-authored-by: BayoNet <da-daos@yandex.ru>
Co-authored-by: Olga Revyakina <revolg@yandex-team.ru>
Co-authored-by: BayoNet <da-daos@yandex.ru>
Before this patch there was:
- parallel_distributed_insert_select=1, that executes:
INSERT INTO dist_out SELECT ... FROM underlying_dist_in
After this patch there will be:
- parallel_distributed_insert_select=2, that executes:
INSERT INTO underlying_dist_out SELECT ... FROM underlying_dist_in
And cover the behaviour w/o integration test, by using the following
techincs:
- SYSTEM STOP DISTRIBUTED SENDS
- prefer_localhost_replica=0
* add EN description
* changes after review
* add RU version
* Update docs/en/operations/settings/settings.md
Co-authored-by: Ivan Blinkov <github@blinkov.ru>
* DOCSUP-711: (en) In settings added description for output_format_json_quote_denormals.
* DOCSUP-711: Fix invalid anchor.
* DOCSUP-711: (ru) In settings added description for output_format_json_quote_denormals.
* DOCSUP-711: Change values styles.
* DOCSUP-711: Add a link from the setting description to the JSON format description. (by pr comment)
Add a link from the JSON format description to the setting description. (by pr comment)
* DOCSUP-711: Rewrite sentence.
* DOCSUP-711: (ru) Added link from settings.md to JSON format.
* DOCSUP-711: (en) Added example of output with the setting (by pr comment).
* DOCSUP-711: Add example of output with the setting.
* DOCSUP-711: Minor fix.
* DOCSUP-711: Update example of settings using.
* DOCSUP-711: Minor fix.
* Update docs/en/interfaces/formats.md by pr
Co-authored-by: BayoNet <da-daos@yandex.ru>
* [wip]Update docs/en/operations/settings/settings.md
Co-authored-by: BayoNet <da-daos@yandex.ru>
* DOCSUP-711: (en) Add sample table and fix pr comments.
* DOCSUP-711: (ru) Updated from en and by pr comments.
* DOCSUP-711: (ru) Updated from en and by pr comments.
* DOCSUP-711: Added name for sample table.
* Update docs/ru/operations/settings/settings.md by pr comment
Co-authored-by: BayoNet <da-daos@yandex.ru>
* Update docs/ru/interfaces/formats.md by pr comment
Co-authored-by: BayoNet <da-daos@yandex.ru>
* Update settings.md
* Update settings.md
Co-authored-by: romanzhukov <romanzhukov@yandex-team.ru>
Co-authored-by: BayoNet <da-daos@yandex.ru>
Without explicitly defined unit of measurement the description for
setting `max_insert_block_size` may result into confusion and mistakenly
interpret as bytes.
