partitioned tables in config #23

New issue

Open

opened 2019-05-24 10:34:28 +00:00 by mkabilov · 0 comments

mkabilov commented

2019-05-24 10:34:28 +00:00

(Migrated from github.com)

in case of setting up replication for child tables of the partitioned table it will be useful to specify pattern for tables, i.e. instead of :

    partitions.report_2017_03_01:
        main_table: report
        engine: CollapsingMergeTree
        init_sync_skip_truncate: true
    partitions.report_2017_04_01:
        main_table: report
        engine: CollapsingMergeTree
        init_sync_skip_truncate: true
    partitions.report_2017_05_01:
        main_table: report
        engine: CollapsingMergeTree
        init_sync_skip_truncate: true
    partitions.report_2017_01_01:
        main_table: report
        engine: CollapsingMergeTree
        init_sync_skip_truncate: true

write something like that:

    partitions.report_*:
        main_table: report
        engine: CollapsingMergeTree
        init_sync_skip_truncate: true

TBD

in case of setting up replication for child tables of the partitioned table it will be useful to specify pattern for tables, i.e. instead of : ```yaml partitions.report_2017_03_01: main_table: report engine: CollapsingMergeTree init_sync_skip_truncate: true partitions.report_2017_04_01: main_table: report engine: CollapsingMergeTree init_sync_skip_truncate: true partitions.report_2017_05_01: main_table: report engine: CollapsingMergeTree init_sync_skip_truncate: true partitions.report_2017_01_01: main_table: report engine: CollapsingMergeTree init_sync_skip_truncate: true ``` write something like that: ```yaml partitions.report_*: main_table: report engine: CollapsingMergeTree init_sync_skip_truncate: true ``` TBD

👍 4

This discussion has been locked. Commenting is limited to contributors.