Re: default_time_to_live vs TTL on insert statement

Okay so it means regular update and any ttl set with write overrides default setting. Which means datastax documentation is incorrect and should be updated. Sent from my iPhone > On Jul 12, 2018, at 9:35 AM, DuyHai Doan wrote: > > To set TTL on a column only and not on the whole CQL row, use U

Re: default_time_to_live vs TTL on insert statement

To set TTL on a column only and not on the whole CQL row, use UPDATE instead: UPDATE USING TTL xxx SET = WHERE partition=yyy On Thu, Jul 12, 2018 at 2:42 PM, Nitan Kainth wrote: > Kurt, > > It is same mentioned on apache docuemtation too, I am not able to find it > right now. > > But my questi

Re: default_time_to_live vs TTL on insert statement

Kurt, It is same mentioned on apache docuemtation too, I am not able to find it right now. But my question is: How to set TTL for a whole column? On Wed, Jul 11, 2018 at 11:36 PM, kurt greaves wrote: > The Datastax documentation is wrong. It won't error, and it shouldn't. If > you want to fix

Re: default_time_to_live vs TTL on insert statement

The Datastax documentation is wrong. It won't error, and it shouldn't. If you want to fix that documentation I suggest contacting Datastax. On 11 July 2018 at 19:56, Nitan Kainth wrote: > Hi DuyHai, > > Could you please explain in what case C* will error based on documented > statement: > > You

Re: default_time_to_live vs TTL on insert statement

Hi DuyHai, Could you please explain in what case C* will error based on documented statement: You can set a default TTL for an entire table by setting the table's default_time_to_live propert

Re: default_time_to_live vs TTL on insert statement

default_time_to_live property applies if you don't specify any TTL on your CQL statement However you can always override the default_time_to_live

Re: default_time_to_live setting in time series data

Thanks for the quick response. TWCS is used. > On 12 Jan 2018, at 11:38 AM, Jeff Jirsa wrote: > > Probably not in any measurable way. > > -- > Jeff Jirsa > > >> On Jan 11, 2018, at 6:16 PM, Eunsu Kim wrote: >> >> Hi everyone >> >> We are collecting monitoring data in excess of 100K TPS

Re: default_time_to_live setting in time series data

Probably not in any measurable way. -- Jeff Jirsa > On Jan 11, 2018, at 6:16 PM, Eunsu Kim wrote: > > Hi everyone > > We are collecting monitoring data in excess of 100K TPS in Cassandra. > > All data is time series data and must have a TTL. > > Currently we have set default_time_to_liv

Re: default_time_to_live setting in time series data

No. Nothing measurable. In fact it should be beneficial if paired with TWCS On 12 Jan. 2018 1:17 pm, "Eunsu Kim" wrote: Hi everyone We are collecting monitoring data in excess of 100K TPS in Cassandra. All data is time series data and must have a TTL. Currently we have set default_time_to_liv

RE: default_time_to_live

www.be-mobile.be<http://www.be-mobile.be/> Email: pieter.callewa...@be-mobile.be<mailto:pieter.callewa...@be-mobile.be> Tel: + 32 9 330 51 80 From: Sylvain Lebresne [mailto:sylv...@datastax.com] Sent: dinsdag 1 oktober 2013 19:10 To: user@cassandra.apache.org Subject: Re: default

Re: default_time_to_live

You're not supposed to change the table settings by modifying system.schema_columnfamilies as this will skip proper propagation of the change. Instead, you're supposed to do an ALTER TABLE, so something like: ALTER TABLE hol WITH default_time_to_live=10; That being said, if you restart the node