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=17&rev2=18 -------------------------------------------------- Range tuples can be encoded in a very similar fashion to the value tuples represented above, except that they always come in pairs. It will likely make sense to store them in a separate blob from the value tuples, since they will bear very little similarity to one another (TODO: need to confirm with an anecdote or two). - || ''name1'' - ''left'' || ''name1'' - ''right'' || ''parent_change'' || + || ''name1'' - ''left'' || ''name1'' - ''right'' || ''parent_change'' || ''null?'' || - || havarti || muenster || 0 || + || havarti || muenster || 0 || 0 || - || || || 1 || + || || || 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.
