Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=thelastpickle.com; h=message-id
	:from:to:in-reply-to:content-type:content-transfer-encoding
	:mime-version:subject:date:references; q=dns; s=
	thelastpickle.com; b=y7hlmcc6BF3EGeoqNWxL7+nnosoII6gzcii0Q7vwHW6
	S/Wc+RrEGm5DE1cvzMU8q9Z1kNtBI2iCLaYKTUq9HL0PjJvk0guCzUBp6pG3L7Yv
	B1rNjAz2H2ezymRH3Z5YGjp5DX/pcPHcMX0QLnRgnzwlinFvhBdjGUVJfVRvS5Oc
	=
Message-Id: <CE5C605A-FC89-4C5F-A219-D8A77B00239A@thelastpickle.com>
From: Aaron Morton <aaron@thelastpickle.com>
To: "user@cassandra.apache.org" <user@cassandra.apache.org>
In-Reply-To: <4C9A9BF8.8070905@pdf.com>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (iPad Mail 7B500)
Subject: Re: column expiration and rows in 0.7
Date: Thu, 23 Sep 2010 12:47:27 +1200
References: <4C9A9BF8.8070905@pdf.com>

The data will only be physically deleted when a major compaction runs =
and the GCGraceSeconds has passed. You need to trigger the compaction =
using node tool.
=20
http://wiki.apache.org/cassandra/DistributedDeletes

Aaron
On 23 Sep 2010, at 12:14, Alaa Zubaidi <alaa.zubaidi@pdf.com> wrote:

> Hi,
> I am expecting my data size to be around nGB. However, it keeps =
growing and growing.
>=20
> I am setting the gc_grace_seconds for the CF to 5 hours, and I am also =
setting "ttl" for all columns on a row and expecting that these columns =
will be "deleted" after the ttl time, and will be "removed" after =
gc_grace_seonds, and I was told that the if ALL columns are deleted the =
whole row will be deleted as well? is this true or not?
>=20
> Thanks,
>=20
> Alaa Zubaidi
>=20
> PDF Solutions, Inc.
> 333 West San Carlos Street, Suite 700
> San Jose, CA 95110  USA
> Tel: 408-283-5639 (or 408-280-7900 x5639)
> fax: 408-938-6479
> email: alaa.zubaidi@pdf.com
>=20
>=20