Thanks Ellis,
so the common scenario is to store data in one CF and any index (inverted?)
in another CF?
2010/4/30 Jonathan Ellis
> the correct data model is one where you can pull the data you want out
> as a slice of a row, or (sometimes) as a slice of sequential rows.
> usually this involv
the correct data model is one where you can pull the data you want out
as a slice of a row, or (sometimes) as a slice of sequential rows.
usually this involves writing the same data to multiple columnfamilies
at insertion time, so when you do queries you don't need to do joins.
On Wed, Apr 28, 201
Hello,
our company has a huge table in a relational database which keeps statistics
of some financional operations.
It looks like the following:
SERVER_ID - server, which served the transaction
ACCOUNT_FROM - account1
ACCOUNT_TO - account2
HOUR - time range for this statistics row (from 0 minutes
