so first limits are good, the unlimited row count of a user can eventually
eat you, which I suspect it is here, you maybe better off partitioning your
data with some reasonable limits, but this is a bigger domain modeling
conversation.
Second, tombstone overflowing is typically a canary for a data
Hi,
I have a table with composite primary id ((userid), id). Some patterns about my
table:
* Each user generally has 0-3000 rows. But there is currently no upper limit.
* Deleting rows for a user is extremely rare, but when done it can be done
thousands of rows at a time.
* The absolutely mo
