Dru Jensen wrote:
JSON+
Question: Is it an acceptable design to use the timestamp as a data
element?
I am currently adding the date to the column name and setting the
number of versions in the table to 1.
Current: htable.put('table','family:date', 'JSON');
What I would like to do is use the timestamp as a data element to
store the date of the entry and set the number of versions to infinite.
Proposed: htable.put ('table', 'family:', 'JSON', 'date');
Is this a good approach? Are there any gotcha's? Is there a way to
get all of the versions for a row/column in a single call? I need to
graph the results over time.
You can do that but why not just use the cell's timestamp/version?
You can get multiple versions using HTable get methods but not using
Scanners currently. With Scanners, only one version -- either at or
just before stipulated timestamp -- is returned.
St.Ack
