You should really get into a habit of disclosing your biases, as you seem to make an appearance in every DuckDB related thread with the same comments:)
(Head of Produck and Co-founder at MotherDuck)
(Head of Produck and Co-founder at MotherDuck)
It has been around since 2016, and it covers and extends the feature set of DuckDB with a huge margin. Worth noting that it never has breaking changes in its table format MergeTree.
I'm tracking the progress of DuckDB and see that it is modeled after ClickHouse, but does not approach it in terms of feature completeness, stability, or performance.
The closest to DuckDB option is to use its self-contained version, clickhouse-local: https://clickhouse.com/blog/extracting-converting-querying-l... or an embedded version, chdb: https://github.com/chdb-io/chdb