cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Trivial Update of "FileFormatDesignDoc" by StuHood
Date Fri, 07 Jan 2011 00:51:37 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "FileFormatDesignDoc" page has been changed by StuHood.
http://wiki.apache.org/cassandra/FileFormatDesignDoc?action=diff&rev1=19&rev2=20

--------------------------------------------------

  || havarti || muenster || 0 || 0 ||
  || || || 1 || 1 ||
  
- This example shows a range tombstone for values at level "name1" between 'havarti' and 'muenster':
the chunk for the "name1" level stores a pair of range tuples for the 'cheese' parent and
a nulls are stored for parents without any range metadata. The end result is that the span
stores a tombstone from ('cheese', 'havarti', <empty>) to ('cheese', 'muenster', null),
where <empty> is the smallest value, and null is the largest value.
+ This example shows a range tombstone for values at level "name1" between 'havarti' and 'muenster':
the chunk for the "name1" level stores a pair of range tuples for the 'cheese' parent and
nulls are stored for parents without any range metadata. The end result is that the span stores
a tombstone from ('cheese', 'havarti', <empty>) to ('cheese', 'muenster', null), where
<empty> is the smallest value, and null is the largest value.
  
  Note that it is not possible for ranges for a parent to overlap: in this case, the ranges
would be resolved such that the intersection was given the winning timestamp, and the two
remainders would use their original timestamps.
  

Mime
View raw message