[ https://issues.apache.org/jira/browse/CASSANDRA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626381#comment-13626381 ]
Jeremy Hanna commented on CASSANDRA-5444: ----------------------------------------- Brandon: to be clear, they saw that when they did the alter table command, it would continue to have the range ghost after the ttl + gc_grace + flush + compact. However if they create a new column family with that gc_grace and do the same process, the range ghost is no longer there. > TTL does not compact rows > -------------------------- > > Key: CASSANDRA-5444 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5444 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.9 > Environment: Linux > Reporter: Sathish > Fix For: 1.1.9 > > > I find that the rows are not compacted when gc_grace_seconds is set through > alter table command. Following were the steps performed: > 1. Created the following table: > CREATE COLUMNFAMILY MirrorSmokeTest ( > id uuid PRIMARY KEY, > test_message varchar > ); > 2. Ran an alter command: > alter table MirrorSmokeTest WITH gc_grace_seconds = 60; > 3. Insert a row into the above table: > insert into MirrorSmokeTest (id, test_message) Values > ('4a7fad82-8298-4d91-85de-8255b7c7e4f5', '2') USING ttl 60; > 4. Waited for 60 seconds and ran a query that results in the following output: > select * from MirrorSmokeTest; > id > -------------------------------------- > 4a7fad82-8298-4d91-85de-8255b7c7e4f5 > 5. Ran a flush and compact and reran the query that results in the following: > select * from MirrorSmokeTest; > id > -------------------------------------- > 4a7fad82-8298-4d91-85de-8255b7c7e4f5 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira