title: cassandra TTL for table behaviour
body: <p>Suppose I inserted a column at second-1 and another column at second-2. Default TTL for table is set to 10 seconds for example:</p>
  
  <p><strong>Question 1</strong>: Is data1 and data2 going to be deleted after 10 seconds or data 1 will be deleted after 10 seconds and data-2 after 11 seconds ( as it was inserted in second-2)? </p>
  
  <p><strong>Question 2</strong>: Is it possible to set a TTL at a table level in such a way that each entry in the table will expire based on the TTL in a FIFO fashion ? (data-1 will expire at second-10 and data-2 at second-11), without specifying TTL while inserting for each data point? (Should be able to specify at a table level ?)</p>
  
  <p>Thanks for the help :)</p>
  
  <p><strong>EDIT</strong>:</p>
  
  <p>the page at <a href="https://docs.datastax.com/en/cql/3.1/cql/cql_using/use_expire_c.html" rel="nofollow noreferrer">https://docs.datastax.com/en/cql/3.1/cql/cql_using/use_expire_c.html</a> says </p>
  
  <blockquote>
    <p>Setting a TTL for a table</p>
    
    <p>The CQL table definition supports the default_time_to_live property,
    which applies a specific TTL to each column in the table. After the
    default_time_to_live TTL value has been exceed, Cassandra tombstones
    the entire table. Apply this default TTL to a table in CQL using
    CREATE TABLE or ALTER TABLE </p>
  </blockquote>
  
  <p>they say "entire table" which confused me.</p>