doris-flink-connector VS ClickHouse

Download JAR file: https://github.com/apache/doris-flink-connector/releases/tag/1.4.0

Thanks for reading! This is realized by our latest Flink-Doris-Connector. It supports ingesting data from RDBMS including MySQL, Oracle, and PostgreSQL to Doris. The Connector has built-in Flink CDC and is capable of full update and incremental update. If there is a new table in the source database, it will automatically create the same table in Apache Doris; if there is a schema change in the source, it will automatically obtain the DDL statement and make the same schema change in Doris.

https://gh-api.clickhouse.tech/play?user=play#U0VMRUNUICogRl...

I subscribe to this issue to keep up with updates:

https://github.com/ClickHouse/ClickHouse/issues/29693#issuec...

And ofc, for those that don't know, the official API https://github.com/HackerNews/API

https://github.com/ClickHouse/ClickHouse

We are trying to use CMake in a very limited fashion.

For example, any build time environment checks are forbidden (no "try_compile" scripts), and all configuration for all platforms is fixed.

We don't use it for installation and packaging; it is only used for builds. The builds have to be self-contained.

From this standpoint, there should be no big difference between CMake, Bazel, Buck, GYP, GN, etc.

curl https://clickhouse.com/ | sh

ClickHouse: ClickHouse is an open-source columnar database management system designed for high-performance analytics. It excels at processing large volumes of data and offers real-time querying capabilities. It’s probably the world’s fastest real-time data analytics system: ClickHouse Benchmark.

It is possible to do this entirely in userspace without a custom scheduler.

See the implementation here: https://github.com/ClickHouse/ClickHouse/blob/master/src/Com...

It works and makes significant improvements for the detection of concurrency bugs, including complex logical races in distributed scenarios.

ClickHouse has support for trailing commas for several years.

I recommend looking at ClickHouse (https://github.com/ClickHouse/ClickHouse/) as an example of a modern SQL database that emphasizes developer experience, performance, and quality-of-life improvements.

I'm the author of ClickHouse, and I'm happy to see that its innovation has been inspired and adopted in other database management systems.

Further investigation revealed that these ports provided direct access to a publicly exposed ClickHouse database—entirely unprotected and requiring no authentication. This discovery raised immediate security concerns, as ClickHouse is an open-source, columnar database management system designed for high-speed analytical queries on massive datasets. Originally developed by Yandex, ClickHouse is widely used for real-time data processing, log storage, and big data analytics—making such an exposure particularly sensitive and valuable from a security standpoint.

I would say it doesn't but it is actively working on it

https://github.com/ClickHouse/ClickHouse/issues/52054

The first rule of thumb is to never use functions from glibc (gmtime, localtime, mktime, etc) because half of them are non-thread-safe, and another half use a global mutex, and they are unreasonably slow. The second rule of thumb is to never use functions from C++, because iostreams are slow, and a stringstream can lead to a silent data loss if an exception is thrown during memory allocation.

ClickHouse has the "parseDateTimeBestEffort" function: https://clickhouse.com/docs/en/sql-reference/functions/type-... and here is its source code: https://github.com/ClickHouse/ClickHouse/blob/74d8551dadf735...

Clickhouse also has managed service (https://clickhouse.com/)