ClickHouse/tests/performance/materialized_view_parallel_insert.xml
Azat Khuzhin 8931d3eb6f Do not use SET via <full_query> in perf tests
Since if the connection will be closed (by some reason), then the
setting will not be applied after transparent reconnect (since only
native clickhouse-client can do this, since it parses the query, but
perf tests uses python driver).

Just use inplace SETTINGS clause or <settings>.
2020-11-21 14:02:21 +03:00

33 lines
1.0 KiB
XML

<test>
<preconditions>
<table_exists>hits_10m_single</table_exists>
</preconditions>
<create_query>
CREATE MATERIALIZED VIEW hits_mv ENGINE MergeTree
PARTITION BY toYYYYMM(EventDate)
ORDER BY (CounterID, EventDate, intHash32(UserID))
SAMPLE BY intHash32(UserID)
SETTINGS
parts_to_delay_insert = 5000,
parts_to_throw_insert = 5000
AS
-- don't select all columns to keep the run time down
SELECT CounterID, EventDate, UserID, Title
FROM hits_10m_single
-- do not select anything because we only need column types
LIMIT 0
</create_query>
<fill_query>SYSTEM STOP MERGES</fill_query>
<query>
INSERT INTO hits_mv
SELECT CounterID, EventDate, UserID, Title
FROM hits_10m_single
SETTINGS max_insert_threads=8
</query>
<drop_query>SYSTEM START MERGES</drop_query>
<drop_query>DROP TABLE IF EXISTS hits_mv</drop_query>
</test>