* with the RP: for one ui action, many nodes may be requested, but it's
simpler to balance the cluster
Many nodes good. You will have increased availability if the data is more
widely distributed.
one sweeter(?) partitioner would be a partitioner that would distribute a row
according only
Hi,
We have defined a CF with a composite row key that sounds like (folder id, doc
id).
For our app, one very common pattern is accessing, through one ui action, some
bunch of data with the following row keys: (id, id_1), (id, id_2), (id, id_3)...
So, multiple rows are accessed, but all row
