Cassandra storage engine issues
You are viewing an old version of this article. View
the current version here.
This page lists difficulties and peculiarities of Cassandra Storage Engine. I'm not putting them into bug tracker because it is not clear whether these properties should be considered bugs.
No way to get E(#rows in column family)
There seems to be no way to get even a rough estimate of how many different keys are present in a column family. I'm using an arbitrary value of 1000 now, which causes
- EXPLAINS with rows #100.
- Odd output for DELETE FROM table. For column family with 3 rows, it prints:
MariaDB [j1]> delete from t1; Query OK, 1000 rows affected (0.14 sec)
The "1000 rows affected" part looks scary.
Comments
Comments loading...
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
