Re: 2019 manual deletion of sstables

(repair would be done after all the nodes with obviously deletable sstables were deleted) (we may then do a purge program anyway) (this would seem to get rid of 60-90% of the purgable data without incurring a big round of tombstones and compaction) On Tue, May 7, 2019 at 12:05 PM Carl Mueller wro

2019 manual deletion of sstables

Last my googling had some people doing this back in 2.0.x days, and that you could do it if you brought a node down, removed the desired sstable #'s artifacts (Data/Index/etc), and then started up. Probably also with a clearing of the saved caches. A decent-ish amount of data (256G) in a 2.1 clus

Re: One time major deletion/purge vs periodic deletion

It's possible you'll run into compaction headaches. Likely actually. If you have time-bucketed purge/archives, I'd implement a time bucketing strategy using rotating tables dedicated to a time period so that when an entire table is ready for archiving you just snapshot its sstables and then TRUNCA

Re: One time major deletion/purge vs periodic deletion

The important point to consider is whether you are deleting old data or recently written data. How old/recent depends on your write rate to the cluster and there's no real formula. Basically you want to avoid deleting a lot of old data all at once because the tombstones will end up in new SSTables

Re: One time major deletion/purge vs periodic deletion

ules > > > which will decide the records to be purged or archived and then purged, > > > so cannot rely on TTL. > > > > > > Thanks, > > > Charu > > > > > > From: Jens Rantil > > > Reply-To: "user@cassandra.apache.org"

Re: One time major deletion/purge vs periodic deletion

6, 2018 at 12:34 AM > *To: *"user@cassandra.apache.org" > *Subject: *Re: One time major deletion/purge vs periodic deletion > > > > Sounds like you are using Cassandra as a queue. It's an antibiotic > pattern. What I would do would be to rely on TTL for rem

Re: One time major deletion/purge vs periodic deletion

To: "user@cassandra.apache.org" Subject: Re: One time major deletion/purge vs periodic deletion Sounds like you are using Cassandra as a queue. It's an antibiotic pattern. What I would do would be to rely on TTL for removal of data and use the TWCS compaction strategy to handle remo

Re: One time major deletion/purge vs periodic deletion

Sounds like you are using Cassandra as a queue. It's an antibiotic pattern. What I would do would be to rely on TTL for removal of data and use the TWCS compaction strategy to handle removal and you just focus on insertion. On Tue, Mar 6, 2018, 07:39 Charulata Sharma (charshar) wrote: > Hi, > >

One time major deletion/purge vs periodic deletion

Hi, Wanted the community’s feedback on deciding the schedule of Archive and Purge job. Is it better to Purge a large volume of data at regular intervals (like run A&P jobs once in 3 months ) or purge smaller amounts more frequently (run the job weekly??) Some estimates on the number of d

Re: How to minimize side effects induced by tombstones when using deletion?

> Also, if we repaired once successfully, will the next repair process take a more reasonable time? Depends on if there was a lot of inconsistent data to repair in the first place. Also full repairs or incremental? Repairs are complicated and tricky to get working efficiently. If you're using vnod

Re: How to minimize side effects induced by tombstones when using deletion?

Thanks, we'll try delete range of rows as it seems to fit our scenario. One more question, as you mentioned "repair often" - and we have seen that several times, the official doc, representations, blogs, etc. But when we repair a column family sized to terabytes on a cluster with ~30 nodes, it tak

Re: How to minimize side effects induced by tombstones when using deletion?

Delete using as few tombstones as possible (deleting the whole partition is better than deleting a row; deleting a range of rows is better than deleting many rows in a range). Repair often and lower gc_grace_seconds so the tombstones can be collected more frequently -- Jeff Jirsa > On Jul

How to minimize side effects induced by tombstones when using deletion?

Hi there. We have a keyspace containing tons of records, and deletions are used as enforced by its business logic. As the data accumulates, we are suffering from performance penalty due to tombstones, still confusing about what could be done to minimize the harm, or shall we avoid any deletions

Re: Triggering Deletion/Updation

Thanks Jon , Prem .. Regards,Hari From: Jon Haddad To: user@cassandra.apache.org Cc: Harikrishnan A Sent: Sunday, November 22, 2015 10:57 AM Subject: Re: Triggering Deletion/Updation There's no built in way of doing cascading deletes in Cassandra, I really wouldn't recom

Re: Triggering Deletion/Updation

assandra.apache.org>" > mailto:user@cassandra.apache.org>> > Sent: Friday, November 20, 2015 2:27 PM > Subject: Triggering Deletion/Updation > > Hello, > > I have a generic question. How can I initiate a triggering deletion in > cassandra? > I mean I need to delete few rows/Partition itself from other tables based on > a status change in another table. > > Thanks & Regards, > Hari > > >

Re: Triggering Deletion/Updation

to my below query ... > Thanks > Hari > > -- > *From:* Harikrishnan A > *To:* "user@cassandra.apache.org" > *Sent:* Friday, November 20, 2015 2:27 PM > *Subject:* Triggering Deletion/Updation > > Hello, > > I have a g

Re: Triggering Deletion/Updation

Trying for second time to get some insights to my below query ...ThanksHari From: Harikrishnan A To: "user@cassandra.apache.org" Sent: Friday, November 20, 2015 2:27 PM Subject: Triggering Deletion/Updation Hello, I have a generic question.  How can I initiate a triggerin

Triggering Deletion/Updation

Hello, I have a generic question.  How can I initiate a triggering deletion in cassandra? I mean I need to delete few rows/Partition itself from other tables based on a status change in another table.   Thanks & Regards,Hari

Re: Record deletion job

No, this is what TTL is for. If you want to schedule a cron to delete data this will need to be an external task. On 19 June 2015 at 07:41, anil_ah wrote: > Hi >Is their any way to schedule a job in cassandra to delete the recrods > which are older than a specific time period. > > Excludin

Record deletion job

Hi    Is their any way to schedule a job in cassandra to delete the recrods which are older than a specific time period.  Excluding the option of TTL. Regards  Anil  Sent from Samsung Mobile

Re: Counter Deletion in a window

On Tue, Nov 18, 2014 at 8:38 AM, Ahmy Yulrizka wrote: > > > 1. Is this a proper use of a counter > It seems reasonable. > 2. would the delete operation has impact on performance ? > Depending on how you query the data, no. If you restrict the query to not cover times where you have deleted t

Counter Deletion in a window

Hi I'm very new with cassandra and I've created a schema like this CREATE TABLE statistics.stats_count ( id text, metric text, resolution text, time timestamp, value counter, PRIMARY KEY ((id, metric, resolution), time) ) Below is an example of data. This data basically j

Re: Cassandra SSTable deletion/load reporting question

> 1.2 w/ vnodes using LeveledCompactionStrategy, using 128 mb SSTables. If you are using LCS the amount of overwritten / deleted data left will be small. Your row will be present in only 1 sstable per level. The number of levels is included in the output from nodetool cfstats on the sstable cou

Re: Cassandra SSTable deletion/load reporting question

Thanks Rob. Will checkout the tool you linked to. In our case it's definitely not the tombstones hanging around since we write entire rows at once and the amount of data in a row is far, far greater than the space a tombstone takes. Jasdeep On Fri, Oct 25, 2013 at 1:14 PM, Robert Coli wrote:

Re: Cassandra SSTable deletion/load reporting question

On Fri, Oct 25, 2013 at 1:10 PM, Jasdeep Hundal wrote: > > After performing a large set of deletes on our cluster, a few hundred > gigabytes work (essentially cleaning out nearly all old data), we noticed > that nodetool reported about the same load as before. > Tombstones are purgeable only aft

Cassandra SSTable deletion/load reporting question

Does anyone have a good explanation or pointers to docs for understanding how Cassandra decides to remove SSTables from disk? After performing a large set of deletes on our cluster, a few hundred gigabytes work (essentially cleaning out nearly all old data), we noticed that nodetool reported about

Re: [deletion in the future]

On 20 July 2013 15:16, Alexis Rodríguez wrote: > That's exactly what is happening with my row, but not what I was trying to > do. It seems that I misunderstood the stackoverflow post. I was trying to > schedule a delete for an entire row, is using ttl for columns the only way? > Yes, there's no

Re: [deletion in the future]

36 AM, Richard Low wrote: > On 19 July 2013 23:31, Alexis Rodríguez wrote: > >> Hi guys, >> >> I've read here [1] that you can make a deletion mutation "for" the >> future. That mechanism operates as a schedule for deletions according to >> the stack

Re: [deletion in the future]

On 19 July 2013 23:31, Alexis Rodríguez wrote: > Hi guys, > > I've read here [1] that you can make a deletion mutation "for" the future. > That mechanism operates as a schedule for deletions according to the > stackoverflow post. But, I've been having problems

[deletion in the future]

Hi guys, I've read here [1] that you can make a deletion mutation "for" the future. That mechanism operates as a schedule for deletions according to the stackoverflow post. But, I've been having problems to make it work with my thrift c++ client. I believe it's related

Re: Deletion use more space.

nks, But Michael's answer confuse me more. > > I use list cf; in cassandra-cli. It seems lots of rows have been deleted, but > keys exist. > > After the deletion, why the key still exists? It seems useless. > > RowKey: 303030303130636563386235643763

Re: Deletion use more space.

Thanks, But Michael's answer confuse me more. I use list cf; in cassandra-cli. It seems lots of rows have been deleted, but keys exist. After the deletion, why the key still exists? It seems useless. RowKey: 30303030313063656338623564376363653038613034333431376565313

Re: Deletion use more space.

; Thank you! > It should be "update column family ScheduleInfoCF with gc_grace = 3600;" > Faint. > > - 原始邮件 - > 发件人: "杨辉强" > 收件人: user@cassandra.apache.org > 发送时间: 星期二, 2013年 7 月 16日 下午 6:15:12 > 主题: Re: Deletion use more space. > > Hi, &g

Re: Deletion use more space.

ou! > It should be "update column family ScheduleInfoCF with gc_grace = 3600;" > Faint. > > - 原始邮件 - > 发件人: "杨辉强" > 收件人: user@cassandra.apache.org > 发送时间: 星期二, 2013年 7 月 16日 下午 6:15:12 > 主题: Re: Deletion use more space. > > Hi, >

Re: Deletion use more space.

Thank you! It should be "update column family ScheduleInfoCF with gc_grace = 3600;" Faint. - 原始邮件 - 发件人: "杨辉强" 收件人: user@cassandra.apache.org 发送时间: 星期二, 2013年 7 月 16日 下午 6:15:12 主题: Re: Deletion use more space. Hi, I use the follow cmd to update gc_grace_secon

Re: Deletion use more space.

- 原始邮件 - 发件人: "Michał Michalski" 收件人: user@cassandra.apache.org 发送时间: 星期二, 2013年 7 月 16日 下午 5:51:49 主题: Re: Deletion use more space. Deletion is not really "removing" data, but it's adding tombstones (markers) of deletion. They'll be later merged with existi

Re: Deletion use more space.

Deletion is not really "removing" data, but it's adding tombstones (markers) of deletion. They'll be later merged with existing data during compaction and - in the end (see: gc_grace_seconds) - removed, but by this time they'll take some space. http://

Deletion use more space.

Hi, all: I use cassandra 1.2.4 and I have 4 nodes ring and use byte order partitioner. I had inserted about 200G data in the ring previous days. Today I write a program to scan the ring and then at the same time delete the items that are scanned. To my surprise, the cassandra cost more di

Re: Time series data and deletion

On Mon, Mar 11, 2013 at 11:25 AM, Flavio Baronti wrote: > > > One more question. I read and reread your description of deletes [1], but > I still am confused on tombstones and GCGraceSeconds, specifically when you > say "If the deletion is before gcBefore it is totally i

Re: Time series data and deletion

We're still on 1.0.12, I'll push for an upgrade. One more question. I read and reread your description of deletes [1], but I still am confused on tombstones and GCGraceSeconds, specifically when you say "If the deletion is before gcBefore it is totally ignored". Suppose I delete

Re: Time series data and deletion

> I'm trying to understand what will happen when we start deleting the old data. Are you going to delete data or use the TTL? > With size tiered compaction, suppose we have one 160Gb sstable and some > smaller tables totalling 40Gb. Not sure on that, it depends on the work load. > My understan

Time series data and deletion

Hello, we are using Cassandra for storing time series data. We never update, only append; we plan to store 1 year worth of data, occupying something around 200Gb. I'm trying to understand what will happen when we start deleting the old data. With size tiered compaction, suppose we have one 160

Re: Deletion consistency

*Mike*, for now I can't upgrade my cluster. I'm going to check the servers time sync. Thanks; *Bryan*, so u think it's not a distributed deleted problem. Thanks for bringing it up. Btw, hector should not be hiding any exception from me. Although there's a mutator reuse in my application. I'm gonna

Re: Deletion consistency

With a RF and CL of one, there is no replication so there can be no issue with distributed deletes. Writes (and reads) can only go to the one host that has the data and will be refused if that node is down. I'd guess that your app isn't deleting records when you think that it is, or that the dele

Re: Deletion consistency

If you increase the number of nodes to 3, with an RF of 3, then you should be able to read/delete utilizing a quorum consistency level, which I believe will help here. Also, make sure the time of your servers are in sync, utilizing NTP, as drifting time between you client and server could caus

Deletion consistency

hello everyone! I have a column family filled with event objects which need to be processed by query threads. Once each thread query for those objects(spread among columns bellow a row), it performs a delete operation for each object in cassandra. It's done in order to ensure that these events won

Re: Cassandra 1.0 row deletion

> If you use the remove function to delete an entire row, is that an atomic > operation? Yes. Row level deletes are atomic. cheers - Aaron Morton Freelance Developer @aaronmorton http://www.thelastpickle.com On 17/08/2012, at 3:39 PM, Derek Williams wrote: > On Thu, Aug 16,

Re: Cassandra 1.0 row deletion

On Thu, Aug 16, 2012 at 9:08 PM, Terry Cumaranatunge wrote: > > We have a Cassandra 1.0 cluster that we run with RF=3 and perform > operations using a consistency level of quorum. We use batch_mutate for all > inserts and updates for atomicity across column families with the same row > key, but use

Cassandra 1.0 row deletion

Hi, We have a Cassandra 1.0 cluster that we run with RF=3 and perform operations using a consistency level of quorum. We use batch_mutate for all inserts and updates for atomicity across column families with the same row key, but use the thrift interface remove API call in C++ to delete a row so t

Re: Mass deletion -- slowing down

Thanks for the note. Ideally I would not like to keep track of what is the oldest indexed date, because this means that I'm already creating a bit of infrastructure on top of my database, with attendant referential integrity problems. But I suppose I'll be forced to do that. In addition, I'll h

Re: Mass deletion -- slowing down

i think what he means is...do you know what day the 'oldest' day is? eg if you have a rolling window of say 2 weeks, structure your query so that your slice range only goes back 2 weeks, rather than to the beginning of time. this would avoid iterating over all the tombstones from prior to the

Re: Mass deletion -- slowing down

> I'm not sure I entirely follow. By the oldest data, do you mean the > primary key corresponding to the limit of the time horizon? Unfortunately, > unique IDs and the timstamps do not correlate in the sense that > chronologically > "newer" entries might have a smaller sequential ID. That's because

Re: Mass deletion -- slowing down

Thanks Peter, I'm not sure I entirely follow. By the oldest data, do you mean the primary key corresponding to the limit of the time horizon? Unfortunately, unique IDs and the timstamps do not correlate in the sense that chronologically "newer" entries might have a smaller sequential ID. That's

Re: Mass deletion -- slowing down

Brandon, it won't work in my application, as I need a few indexes on attributes of the job. In addition, a large portion of queries is based on key-value lookup, and that key is the unique job ID. I really can't have data packed in one row per day. Thanks, Maxim On 11/13/2011 8:34 PM, Brandon

Re: Mass deletion -- slowing down

> I do limit the number of rows I'm asking for in Pycassa. Queries on primary > keys still work fine, Is it feasable in your situation to keep track of the oldest possible data (for example, if there is a single sequential writer that rotates old entries away it could keep a record of what the old

Re: Mass deletion -- slowing down

On Sun, Nov 13, 2011 at 7:25 PM, Maxim Potekhin wrote: > Each row represents a computational task (a job) executed on the grid or in > the cloud. It naturally has a timestamp as one of its attributes, > representing the time of the last update. This timestamp > is used to group the data into "buck

Re: Mass deletion -- slowing down

Brandon, thanks for the note. Each row represents a computational task (a job) executed on the grid or in the cloud. It naturally has a timestamp as one of its attributes, representing the time of the last update. This timestamp is used to group the data into "buckets" each representing one da

Re: Mass deletion -- slowing down

On Sun, Nov 13, 2011 at 6:55 PM, Maxim Potekhin wrote: > Thanks to all for valuable insight! > > Two comments: > a) this is not actually time series data, but yes, each item has > a timestamp and thus chronological attribution. > > b) so, what do you practically recommend? I need to delete > half

Re: Mass deletion -- slowing down

Thanks to all for valuable insight! Two comments: a) this is not actually time series data, but yes, each item has a timestamp and thus chronological attribution. b) so, what do you practically recommend? I need to delete half a million to a million entries daily, then insert fresh data. What's

Re: Mass deletion -- slowing down

Deletions in Cassandra imply the use of tombstones (see http://wiki.apache.org/cassandra/DistributedDeletes) and under some circumstances reads can turn O(n) with respect to the amount of columns deleted, depending. It sounds like this is what you're seeing. For example, suppose you're inserting a

Re: Mass deletion -- slowing down

I tried > two methods of deletion -- individual cf.remove() as well as batch removal > in Pycassa. > What happens after that is as follows: attempts to read the same CF, using > the same index values start to time out in the Pycassa client (there is a > thrift message about timeout). Th

Re: Mass deletion -- slowing down

I've done more experimentation and the behavior persists: I start with a normal dataset which is searcheable by a secondary index. I select by that index the entries that match a certain criterion, then delete those. I tried two methods of deletion -- individual cf.remove() as well as

Mass deletion -- slowing down

Hello, My data load comes in batches representing one day in the life of a large computing facility. I index the data by the day it was produced, to be able to quickly pull data for a specific day within the last year or two. There are 6 other indexes. When it comes to retiring the data, I in

Re: After column deletion cassandra won't insert more data to a specific key

gt; > On 26 Jul 2011, at 04:25, Guillermo Winkler wrote: > > Hi, thanks both for the answers. > > The problem was indeed with the timestamps. > > What was happening also was that in a mutation involving 1 deletion and > various insertions for the same key, all were using the same t

Re: After column deletion cassandra won't insert more data to a specific key

both for the answers. > > The problem was indeed with the timestamps. > > What was happening also was that in a mutation involving 1 deletion and > various insertions for the same key, all were using the same timestamp, so > beside looking at the code doing this > > remov

Re: After column deletion cassandra won't insert more data to a specific key

Hi, thanks both for the answers. The problem was indeed with the timestamps. What was happening also was that in a mutation involving 1 deletion and various insertions for the same key, all were using the same timestamp, so beside looking at the code doing this remove key insert key, col, val

Re: After column deletion cassandra won't insert more data to a specific key

Remember the cli uses microsecond precision . so if your app is not using the same precision weird this will result in clients writing the biggest timsetamp winning the final value. On Saturday, July 23, 2011, Jonathan Ellis wrote: > You must have given it a delete timestamp in the "future." > >

Re: After column deletion cassandra won't insert more data to a specific key

You must have given it a delete timestamp in the "future." On Sat, Jul 23, 2011 at 3:46 PM, Guillermo Winkler wrote: > I'm having a strange behavior on one of my cassandra boxes, after all > columns are removed from a row, insertion on that key stops working (from > API and from the cli) > [defau

Re: After column deletion cassandra won't insert more data to a specific key

Sorry, Cassandra version is 0.7.4 On Sat, Jul 23, 2011 at 5:46 PM, Guillermo Winkler wrote: > I'm having a strange behavior on one of my cassandra boxes, after all > columns are removed from a row, insertion on that key stops working (from > API and from the cli) > > [default@Agent] get Schedule

After column deletion cassandra won't insert more data to a specific key

I'm having a strange behavior on one of my cassandra boxes, after all columns are removed from a row, insertion on that key stops working (from API and from the cli) [default@Agent] get Schedulers['atendimento']; Returned 0 results. [default@Agent] set Schedulers['atendimento']['test'] = 'dd'; Val

Re: deletion questions

ed CF which used 90% of > available > space. After issuing a "drop column family User;" command > no *User*.db files were deleted. "nodetool compact" haven't helped too. > How > can that deletion be triggered?" > > You have to wait for a garbage co

Re: deletion questions

"2. Trying to reduce disk occupation I deleted CF which used 90% of available space. After issuing a "drop column family User;" command no *User*.db files were deleted. "nodetool compact" haven't helped too. How can that deletion be triggered?" You have to

deletion questions

Hello, I'm trying to use Cassandra 0.8.1 as a media storage where the stored items have some TTL. So that I need to somehow delete and purge obsoleted items. I've played with deletion columns from db by using Thift CassandraClient::remove call, but faced with the problem that sstable fi

Re: Re : pb deletion

o remove records from my > application but these records were created before from CLI. > is there a explication for this? > > > De : Peter Schuller > À : user@cassandra.apache.org > Envoyé le : Vendredi 27 Mai 2011 19h05 > Objet : Re: pb deleti

Re : pb deletion

: pb deletion > i use cassandra database replicated in two servers,when want to delete a > record using this line : > client.remove(keyspace, sKey, new ColumnPath(columnFamily), timestamp, > ConsistencyLevel.ONE); > > but when i check,i see that the record still exist! Are

Re: pb deletion

ot;real" timestamp such that the deletion is stamped higher than the insertion? -- / Peter Schuller

Re: pb deletion

one (that has not had the delete propagated to it). Try removing with a ConsistencyLevel.QUORUM or ConsistencyLevel.ALL (same thing in your case). - Original Message - From: "karim abbouh" To: user@cassandra.apache.org Sent: Friday, May 27, 2011 5:09:08 PM Subject: pb de

pb deletion

i use cassandra database replicated in two servers,when want to delete a record using this line : client.remove(keyspace, sKey, new ColumnPath(columnFamily), timestamp, ConsistencyLevel.ONE); but when i check,i see that the record still exist! any idea BR

A query in deletion of a row

Hello, > > I am unclear on Why deleting a row in Cassandra does not delete a row key? > Is an empty row never deleted from Column Family? > > It would be of great help if someone can elaborate on this. > > Thanks, > Anuya >

Re: InvalidRequestException: Mutation must have one ColumnOrSuperColumn or one Deletion

u, Mar 17, 2011 at 8:13 AM, Anurag Gujral > > wrote: > >> > >> Hi All, > >> I am using function batch_mutate of cassandra 0.7 and I am > >> getting the error InvalidRequestException: Mutation must have one > >> ColumnOrSuper

Re: InvalidRequestException: Mutation must have one ColumnOrSuperColumn or one Deletion

   I am using function batch_mutate of cassandra 0.7 and I am >> getting the error InvalidRequestException: Mutation must have one >> ColumnOrSuperColumn or one Deletion. I have my own C++ cassandra client >> using thrift 0.0.5 api. >> >> Any S

Re: InvalidRequestException: Mutation must have one ColumnOrSuperColumn or one Deletion

mutate of cassandra 0.7 and I am > getting the error InvalidRequestException: Mutation must have one > ColumnOrSuperColumn or one Deletion. I have my own C++ cassandra client > using thrift 0.0.5 api. > > Any Suggestions. > > Sample Code > map > cfmap; > >

Re: InvalidRequestException: Mutation must have one ColumnOrSuperColumn or one Deletion

olumn or one Deletion. I have my own C++ cassandra client > using thrift 0.0.5 api. > > Any Suggestions. > > Sample Code > map > cfmap; > > vector mutations; > >Column temp_col; > temp_col.name.assign("abcd"); > temp_col.v

InvalidRequestException: Mutation must have one ColumnOrSuperColumn or one Deletion

Hi All, I am using function batch_mutate of cassandra 0.7 and I am getting the error InvalidRequestException: Mutation must have one ColumnOrSuperColumn or one Deletion. I have my own C++ cassandra client using thrift 0.0.5 api. Any Suggestions. Sample Code map > cfmap; vec

Re: Rows and deletion

return them once you've reached the page size? > > Regards, > Ásgeir > > From: Tyler Hobbs [mailto:ty...@datastax.com] > Sent: 21. febrúar 2011 23:20 > To: user@cassandra.apache.org > Subject: Re: Rows and deletion > > Since its not posible t

RE: Rows and deletion

Thanks for the fast response but that would be quite difficult on paging results, do you know if there is a fix in the works? Regards, Ásgeir From: Tyler Hobbs [mailto:ty...@datastax.com] Sent: 21. febrúar 2011 23:20 To: user@cassandra.apache.org Subject: Re: Rows and deletion

Re: Rows and deletion

> > Since its not posible to get accurate row range list because of ghost rows > atm. What is the best solution to get accurate list without ghosts. > Page through all of the rows normally, but skip rows which have zero columns. -- Tyler Hobbs Software Engineer, DataStax

Rows and deletion

Hi, Since its not posible to get accurate row range list because of ghost rows atm. What is the best solution to get accurate list without ghosts. What I am doing is listing objects that has more data in detail. Regards, Ásgeir Halldórsson

Re: Deletion via SliceRange

It's not on anyone's short list, that I know of. https://issues.apache.org/jira/browse/CASSANDRA-494 On Tue, Jan 4, 2011 at 5:18 PM, mike dooley wrote: > any idea when Deletion via SliceRanges will be supported? > >     [java] Caused by: InvalidRequestException(why:De

Deletion via SliceRange

any idea when Deletion via SliceRanges will be supported? [java] Caused by: InvalidRequestException(why:Deletion does not yet support SliceRange predicates.) [java] at org.apache.cassandra.thrift.Cassandra$batch_mutate_result.read(Cassandra.java:16477) thanks, -mike

Re: RE: deletion

Ah, I see code in /thrift/ThriftValidation .javathrow new InvalidRequestException("Deletion does not yet support SliceRange predicates.");Sorry about that, did not fully understand what you were saying. I've done something similar where I did a get slice get_slice then sent a sing

RE: deletion

alize that supercolumns had that limitation. ticker:measure fields indeed seem to make sense. That's a relative easy switch. I could indeed add the day to the field (so ticker:measure:day) to enable easy deletion of days. However this doesn't feel very clean. I would prefer to keep us

Re: deletion

every value for the day or delete the entire day easily.For your deletion issue, batch_mutate is your friend. The Deletion struct lets you delete:- a row, by excluding the predicate and super_column- a super_column by including super_column and not predicate - a columnSome of the things that were

deletion

). How would I go about doing that? First a multiget_slice and then a remove command for each value? Or am I missing an easier way? Is slice deletion within batch_mutate still scheduled to be implemented? Thanks for your help, Koert

Re: Question regarding consistency and deletion

On Tue, Jul 13, 2010 at 5:47 AM, Samuru Jackson wrote: > Thanks for the links. > > Actually it is pretty easy to catch those tombstoned keys on the > client side. However, in certain applications it can generate some > additional overhead on the network. > > I think it would be nice to have a forc

Re: Question regarding consistency and deletion

andras > terminology- right? > > Is there any way to force the sync/garbage collection of the deletion > of the such empty rows? > > Reading the mailinglist, this behaviour is relating to the weak > consistency of Cassandra. What I don't understand is, why is it &

Re: Question regarding consistency and deletion

t treats a part of a returned slice as deleted or not. Those empty rows are referenced as a Tombstone in Cassandras terminology- right? Is there any way to force the sync/garbage collection of the deletion of the such empty rows? Reading the mailinglist, this behaviour is relating to the weak

Question regarding consistency and deletion

column count if it treats a part of a returned slice as deleted or not. Those empty rows are referenced as a Tombstone in Cassandras terminology- right? Is there any way to force the sync/garbage collection of the deletion of the such empty rows? Reading the mailinglist, this behaviour is relat

Re: KeyRange deletion

ested in avoid round-trips, have you tried using batch_mutate? I know there was a limitation when specifying a Deletion, but I think that has been resolved. On Wed, Jun 23, 2010 at 17:39, Carlos Sanchez wrote: > Would there be any support for a KeyRange (start/end key) deletion in 0.7? &g

KeyRange deletion

Would there be any support for a KeyRange (start/end key) deletion in 0.7? Carlos This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure

  1   2   >