ClickHouse / ClickHouse/dbt-clickhouse
Union all issues
- Dominant language
- Python
- Stars
- 362
- Forks
- 177
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 8
Description
Hi,
We're using DBT and clickhouse. Trouble begins when using UNION ALL , which is a known clickhouse issue: https://github.com/ClickHouse/ClickHouse/issues/30532
As stated in the above it's a very common pattern for BI/DBT.
DBT has a special union macro (https://github.com/dbt-labs/dbt-utils/blob/main/macros/sql/union.sql) which is very useful.
Bottom line, would be very useful to have dbt-clickhouse Materialize a table that uses this macro as a series of INSERTs of each unionized relations, rather than a single CREATE TABLE as SELECT.
Contributor guide
Research direction
Start by examining the dbt-clickhouse table materialization and compare its behavior with the dbt-utils union macro and the linked ClickHouse issue. The work is done when a table built from UNION ALL relations can be materialized through separate inserts rather than one CREATE TABLE AS SELECT, with behavior verified against the project’s existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, python, sql
- Domain
- data-engineering, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100