chdb-io

Draft or update a pull request title and description for the current repository. Use when preparing, creating, or editing a pull request.

Use when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas. Provides chDB DataStore — same pandas API, ClickHouse engine underneath. Also handles reading from S3,…

Use when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB — embedded…

Finish the daily ClickHouse master sync in chdb-core once the upstream diff is applied (.github/nightly/daily_sync.py apply) - resolve its conflicts, build, run the Python tests, fix what the sync broke, and write the notes for the pull request. Use in the…

Sync chdb-core to a newer ClickHouse release without losing chDB-specific behavior. Use for ClickHouse baseline upgrades, large src or contrib updates, submodule changes, sync conflicts, and CI failures after an upgrade. Covers embedded startup and shutdown,…

Use when the user has tabular data (pandas DataFrame, parquet, csv, Arrow, json) and wants to filter, group, aggregate, join, or speed up slow pandas. Provides chDB DataStore — same pandas API, ClickHouse engine underneath. Also handles reading from S3,…

Use when the user wants to run SQL — especially analytical SQL — on local files (parquet/csv/json), URLs, S3 paths, or remote databases (Postgres, MySQL, MongoDB, ClickHouse Cloud, Iceberg, Delta Lake) without setting up a server. Provides chDB — embedded…