Hi all,
I'm thinking about storing payments in the following format:
rowId: senderId (i.e. "acct:123")
CF: "payment@<timestamp>" (i.e. "payment@201406171224000")
CQ: receiverId_edgeId ("acct:456_payment:1001")
Value: properties
Is this a good way to model payment events? The most frequent ops is to get
the last payment, so can I scan the table using a reversed range?
Also I'd like to know if point-in-time status data can be modeled in a
similar fashion, or should I take advantage of the timestamp column.
Cheers,
--
Jianshi Huang
LinkedIn: jianshi
Twitter: @jshuang
Github & Blog: http://huangjs.github.com/
