Which clickhouse engines dose chDB currently support and will support in the future

[DanielMao1]

Hello, I would like to know if there is a list to let me know that, amoung so many engines clickhouse provides, which are supported by chDB? As far as I know, Memory engine has some issues, so I would like to know, which are well supported? (To be more specific, MergeTree, AggregatingMergeTree, Memory are the three types we are now considering to use, I would like to know if they are supported)

Database engines:

Atomic Lazy Replicated PostgreSQL MySQL SQLite MaterializedPostgreSQL MaterializedMySQL

Mergetree engines:

MergeTree Data Replication Custom Partitioning Key ReplacingMergeTree SummingMergeTree AggregatingMergeTree CollapsingMergeTree VersionedCollapsingMergeTree GraphiteMergeTree Approximate Nearest Neighbor Search Indexes [experimental] Full-text Indexes

Log engines:

Log Stripelog TinyLog

Integration engines:

Azure Blob Storage DeltaLake EmbeddedRocksDB ExternalDistributed TimeSeries HDFS Hive Hudi Iceberg JDBC Kafka MaterializedPostgreSQL MongoDB MySQL NATS ODBC PostgreSQL RabbitMQ Redis S3 S3Queue SQLite

special engines:

Distributed Dictionary Merge Executable File Null Set Join URL View Memory Buffer External Data GenerateRandom KeeperMap FileLog

If you still prefer GitHub issues, remove all this text and ask your question here.

[auxten]

Most disk, API, Remote based engine is supported perfectly. For memory engine, the session problem make it can not persist across query function call. But you can still write all SQL into one query call separated by ; to make it work.

[auxten]

Memory engine is supported. See: https://github.com/chdb-io/chdb/blob/main/tests/test_conn_cursor.py