Draft:ChDB

This may take 2 months or more, since drafts are reviewed in no specific order. There are 2,465 pending submissions waiting for review.

Draft:ChDB
  • Comment: Please rewrite from scratch without the use of LLMs. Corporate blogs are not reliable sources. Helpful Raccoon (talk) 23:23, 3 June 2026 (UTC)

chDB
Original authorAuxten Wang
DevelopersClickHouse, Inc.
Release2023
Written inC++, Python
Operating systemmacOS, Linux
TypeEmbedded database, OLAP
LicenseApache License 2.0
Websiteclickhouse.com/docs/chdb
Repositorygithub.com/chdb-io/chdb

chDB is an open-source embedded SQL engine for online analytical processing (OLAP), based on ClickHouse. It runs the ClickHouse query engine in-process, inside a host application, rather than through a separate database server, and is distributed mainly as a Python package under the Apache License 2.0.[1][2] In addition to Python, the project provides bindings for C, C++, Go, JavaScript, Bun, and Rust.[3]

History

chDB was created by Auxten Wang and first published as a Python package in 2023, with version 1.0.0 following in December of that year.[4][5][6] It was acquired by ClickHouse, Inc. in March 2024.[4][2]

Design

Because the ClickHouse engine runs in the same process as the calling application, data moves between them without being copied, so a query can read values already held in memory, such as a pandas DataFrame in a Jupyter notebook, and return its results into the same session.[1]

chDB uses the same SQL as ClickHouse and can read the formats ClickHouse supports, more than 70 in total, among them Parquet, CSV, and JSON.[7][8][9] A single query can combine these with in-memory data and remote sources without loading them into a server first, and a session can keep data between queries for multi-step work.[9] Its Python API works directly with dataframes, which makes it convenient to call from existing data-science code.[10]

Like DuckDB, chDB is an embedded OLAP database, and the two are often compared for local analytics.[11][12] It is mainly an option for developers already working with ClickHouse, especially when a workload relies on ClickHouse-specific SQL features such as array functions.[11][12]

References

  1. ^ a b Schulze, Robert; Schreiber, Tom; Yatsishin, Ilya; Dahimene, Ryadh; Milovidov, Alexey (2024). "ClickHouse - Lightning Fast Analytics for Everyone" (PDF). Proceedings of the VLDB Endowment. 17 (12): 3731–3744. doi:10.14778/3685800.3685802.
  2. ^ a b "chDB". Database of Databases. Carnegie Mellon University Database Group. 14 March 2024. Retrieved 2026-06-04.
  3. ^ "chdb-io/chdb". GitHub. chdb-io. Retrieved 2026-06-04.
  4. ^ a b Milovidov, Alexey; Bragin, Tanya (2024-03-06). "chDB joins the ClickHouse family". ClickHouse Blog. ClickHouse, Inc. Retrieved 2026-06-04.
  5. ^ "chdb 0.2.2". Python Package Index. 2023-03-23. Retrieved 2026-06-04.
  6. ^ "Release v1.0.0". GitHub. chdb-io. 2023-12-01. Retrieved 2026-06-04.
  7. ^ Archer, Cameron (2025-10-27). "ClickHouse vs chDB: let's talk about embedded ClickHouse". Tinybird. Retrieved 2026-06-04.
  8. ^ Orlov, Dmitrii (2024). Knowledge Graphs at Your Fingertips: a Survey of Kaggle Notebooks for Knowledge Graph Analytics (PDF) (Master's thesis). Eindhoven University of Technology.
  9. ^ a b Zhiyanov, Anton (2023-12-11). "Trying chDB, an embeddable ClickHouse engine". Anton Zhiyanov's blog. Retrieved 2026-06-04.
  10. ^ Wang, Xiaoying; Wang, Jiannan; Wang, Tianzheng; Zhang, Yong (2025). "Accio: Bolt-on Query Federation" (PDF). Proceedings of the VLDB Endowment. 18 (7): 2126–2135. doi:10.14778/3734839.3734849.
  11. ^ a b Krupitsky, Daniel (2025-03-25). "Small-Scale Data Pipeline: DuckDB vs. chDB vs. Spark". Digital Turbine. Retrieved 2026-06-04.
  12. ^ a b Roset, Martin-Pierre (2026-04-15). "Embedded Databases in 2026: DuckDB, SQLite, Polars, and chDB". Kestra. Retrieved 2026-06-04.

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.