it will be immediate. But it will fail if not all hosts in the cluster are up, this is the tradeoff. We regard the truncate operation an admin api so I think it's a fair tradeoff.
On Fri, Jun 18, 2010 at 11:50 PM, Phil Stanhope <pstanh...@wimba.com> wrote: > In 0.6.x the iterating approach works ... but you need to flush and compact > (after GCGraceSeconds) in order to NOT see the keys in the CF. > > Will the behavior of the truncate method in 0.7 require flush/compact as > well? Or will it be immediate? > > -phil > > On Jun 18, 2010, at 1:29 PM, Benjamin Black wrote: > > > In 0.6 your only option with those constraints is to iterate over the > > entire CF and deleting row by row. This requires you are either using > > OPP or have an index that covers all keys in the CF. 0.7 adds the > > ability to truncate a CF (deleting all its rows) through the API. > > > > On Fri, Jun 18, 2010 at 10:24 AM, Claire Chang > > <cla...@merchantcircle.com> wrote: > >> programmatically w/o bringing the servers down. > >> > >> thanks, > >> claire > >> > >
