Fix Version/s: 0.7.0 rc 1
The followings are the conversation I had with jbellis on IRC:
have a question on deletion of super column....deletion of SuperColumn works fine....but when I add any new sub-column, the 'old' sub-columns reappear..how can I tell they are tombstoned
the 'old' sub-columns still have all the data in place, including timestamp
and the timestamp is older than markDeletaAt of the super column
<jbellis> appoji: right. that is expected. the subcolumns won't be tombstoned, the supercolumn tombstone should supress them.
<jbellis> appoji: but writing a new subcolumn should resurrect the others. can you submit a test case?
I am able to reproduce it with cli as followings:
1. create column family UserGroup with column_type = 'Super' and gc_grace=5 and comparator = 'AsciiType' and subcomparator = 'BytesType'
2. set UserGroup ['100'] ['memberList']['paul']=''
3. del UserGroup ['100'] ['memberList']
4. wait for 5 seconds and "list UserGroup" does not return any data, which is correct
5. set UserGroup ['100'] ['memberList']['andrew']=''
6. now "list UserGroup" returns 2 sub-columns ('paul' and 'andrew')
here is server log for step 6:
DEBUG 22:40:52,378 range_slice
DEBUG 22:40:52,379 RangeSliceCommand
DEBUG 22:40:52,380 restricted single token match for query [0,0]
DEBUG 22:40:52,381 local range slice
DEBUG 22:40:52,382 collecting 0 of 100: SuperColumn(memberList -delete at 128953
DEBUG 22:40:52,383 scanned DecoratedKey(9839004666223652184852086760848439587, 3