[jira] [Comment Edited] (CASSANDRA-5444) TTL does not compact rows

["Brandon Williams (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626140#comment-13626140 ] 

Brandon Williams edited comment on CASSANDRA-5444 at 4/9/13 2:30 AM:
---------------------------------------------------------------------

Nothing specific to TTLs here, you're dealing with a range ghost (see the FAQ) but they are eliminated in 1.2.
                
      was (Author: brandon.williams):
    Nothing specific to TTLs here, you're dealing with a range ghost (see the FAQ) but they eliminated in 1.2.
                  
> 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