unamedrus

Not only. Transactions, UPDATES, CBO, Better join optimizations.

It seems that someone is stuck in 2016, when there is no good alternatives for ClickHouse exist in open source.

In that case, you should know what is Altinity.

> Lightweight deletes were released to both

Because they were contributed by community member, not ClickHouse Inc core team.

https://github.com/ClickHouse/ClickHouse/pull/37893

Are you part of ClickHouse community, ever used that DBMS or participate in any activity related it?

Just to make sure, we are on the same page.

I just received the same email.

Good for them, moving to nic.ru

Your statement is misleading at least.

In this short article nowhere said that Druid is faster than ClickHouse in 8 times. They claimed: "Druid is simply 2 times faster than ClickHouse" (actually by total runtime it's only 1.5 times faster)

There are also newer ClickHouse benchmark which total runtime = 0.779s This is almost the same number as in Imply statement.

https://altinity.com/blog/ultra-fast-data-loading-and-testin...

> I also need the metadata for the rows to be in something more robust like Postgres or Mongo.

How big is that metadata? If it's less than tens of millions rows, you can look at External Dictionaries support in clickhouse.

https://clickhouse.tech/docs/en/sql-reference/dictionaries/e...

https://altinity.com/blog/2020/5/19/clickhouse-dictionaries-...