Re: Improving performance where a lot of updates and deletes are required?

On 11/08/2016 08:52 PM, Alain Rastoul wrote: For example if you had to track the position of a lot of objects, instead of updating the object records, each second you could insert a new event with : (object: object_id, event_type: position_move, position : x, y ). and add a timestamp of

Re: Improving performance where a lot of updates and deletes are required?

On 11/08/2016 11:05 AM, DuyHai Doan wrote: Are you sure Cassandra is a good fit for this kind of heavy update & delete scenario ? +1 this sounds like relational thinking scenario... (no offense, I like relational systems) As if you want to maintain the state of a lot of entities with updates

Re: Improving performance where a lot of updates and deletes are required?

Yes, as doc says "Expired data is marked with a tombstone" but you save communication with host and processing of DELETE operator. Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Tue, 08 Nov 2016 09:32:16 -0500Ali Akhtar

Re: Improving performance where a lot of updates and deletes are required?

Also in they are being read before compaction: http://docs.datastax.com/en/cql/3.1/cql/cql_using/use_expire_c.html Hannu > On 8 Nov 2016, at 16.36, DuyHai Doan wrote: > > "Does TTL also cause

Re: Improving performance where a lot of updates and deletes are required?

"Does TTL also cause tombstones?" --> Yes, after the TTL expires, at the next compaction the TTLed column is replaced by a tombstone, as per my understanding On Tue, Nov 8, 2016 at 3:32 PM, Ali Akhtar wrote: > Does TTL also cause tombstones? > > On Tue, Nov 8, 2016 at 6:57

Re: Improving performance where a lot of updates and deletes are required?

Does TTL also cause tombstones? On Tue, Nov 8, 2016 at 6:57 PM, Vladimir Yudovin wrote: > >The deletes will be done at a scheduled time, probably at the end of the > day, each day. > > Probably you can use TTL? http://docs.datastax.com/en/ >

Re: Improving performance where a lot of updates and deletes are required?

The deletes will be done at a scheduled time, probably at the end of the day, each day. Probably you can use TTL? http://docs.datastax.com/en/cql/3.1/cql/cql_using/use_expire_c.html Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes.

Re: Improving performance where a lot of updates and deletes are required?

Yes, because there will also be a lot of inserts, and the linear scalability that c* offers is required. But the inserts aren't static, and the data that comes in will need to be updated in response to user events. Data which hasn't been touched for over a week has to be deleted. (Sensitive

Re: Improving performance where a lot of updates and deletes are required?

Are you sure Cassandra is a good fit for this kind of heavy update & delete scenario ? Otherwise, you can always use several tables (one table/day, rotating through 7 days for a week) and do a truncate of the table at the end of the day. On Tue, Nov 8, 2016 at 11:04 AM, Ali Akhtar

Improving performance where a lot of updates and deletes are required?

I have a use case where a lot of updates and deletes to a table will be necessary. The deletes will be done at a scheduled time, probably at the end of the day, each day. Updates will be done throughout the day, as new data comes in. Are there any guidelines on improving cassandra's performance