[jira] [Updated] (CASSANDRA-9672) Provide a per-table param that would force default ttl on all updates

2018-11-18 Thread C. Scott Andreas (JIRA)


 [ 
https://issues.apache.org/jira/browse/CASSANDRA-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

C. Scott Andreas updated CASSANDRA-9672:

Component/s: Distributed Metadata

> Provide a per-table param that would force default ttl on all updates
> -
>
> Key: CASSANDRA-9672
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9672
> Project: Cassandra
>  Issue Type: Improvement
>  Components: Distributed Metadata
>Reporter: Aleksey Yeschenko
>Priority: Minor
>
> Many users have tables that rely on TTL entirely - no deletes, and only fixed 
> TTL value.
> The way that default ttl works now, we only apply it if none is specified.
> We should provide an option that would *enforce* the specified TTL. Not 
> allowing ttl-less {{INSERT}} or {{UPDATE}}, not allowing ttl that's lower or 
> higher than the default ttl, and not allowing deletes.
> That option when enabled ({{force_default_ttl}}) should allow us to drop more 
> tables during compaction and do so cheaper. Would also allow the DBAs to 
> enforce the constraint in a guaranteed manner.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org



[jira] [Updated] (CASSANDRA-9672) Provide a per-table param that would force default ttl on all updates

2015-06-28 Thread Aleksey Yeschenko (JIRA)

 [ 
https://issues.apache.org/jira/browse/CASSANDRA-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aleksey Yeschenko updated CASSANDRA-9672:
-
Description: 
Many users have tables that rely on TTL entirely - no deletes, and only fixed 
TTL value.

The way that default ttl works now, we only apply it if none is specified.

We should provide an option that would *enforce* the specified TTL. Not 
allowing ttl-less {{INSERT}} or {{UPDATE}}, not allowing ttl that's lower or 
higher than the default ttl, and not allowing deletes.

That option when enabled ({{force_default_ttl}}) should allow us to drop more 
tables during compaction and do so cheaper. Would also allow the DBAs to 
enforce the constraint in a guaranteed manner.

  was:
Many users have tables that don't rely on TTL entirely - no deletes, and only 
fixed TTL value.

The way that default ttl works now, we only apply it if none is specified.

We should provide an option that would *enforce* the specified TTL. Not 
allowing ttl-less {{INSERT}} or {{UPDATE}}, not allowing ttl that's lower or 
higher than the default ttl, and not allowing deletes.

That option when enabled ({{force_default_ttl}}) should allow us to drop more 
tables during compaction and do so cheaper.


 Provide a per-table param that would force default ttl on all updates
 -

 Key: CASSANDRA-9672
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9672
 Project: Cassandra
  Issue Type: Improvement
Reporter: Aleksey Yeschenko
Priority: Minor

 Many users have tables that rely on TTL entirely - no deletes, and only fixed 
 TTL value.
 The way that default ttl works now, we only apply it if none is specified.
 We should provide an option that would *enforce* the specified TTL. Not 
 allowing ttl-less {{INSERT}} or {{UPDATE}}, not allowing ttl that's lower or 
 higher than the default ttl, and not allowing deletes.
 That option when enabled ({{force_default_ttl}}) should allow us to drop more 
 tables during compaction and do so cheaper. Would also allow the DBAs to 
 enforce the constraint in a guaranteed manner.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)