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: domain of jbellis@gmail.com designates
 209.85.161.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=Yc9EcvfEA4pmKygvpl8qm1xCXLUIYuj4mZx9d9dex36nNqD2VQvjVRmWs0oNpcsneZ
         2eSIe9g1C5Zf75iFpf8AyG1OWCxul2AHY+iDzpom35X+bSdJ5FvU3hJRKnbY775cEmog
         yFY3OX7wpEIUx/w7KQKNkY8aYBUODS05JoxCM=
MIME-Version: 1.0
In-Reply-To: <AANLkTik+0aGpQpjfErjaFtBAHCLuWO3MrF7oC5qQJUpj@mail.gmail.com>
References: <AANLkTinhsX2UMZwpAtE-usvF97Xb=zk2aRDnmrHaPz7Z@mail.gmail.com>
	<AANLkTi=t0QPmzgTmUQjtgqYTrmPoP+0TnTu3MqtRtZVy@mail.gmail.com>
	<AANLkTik+0aGpQpjfErjaFtBAHCLuWO3MrF7oC5qQJUpj@mail.gmail.com>
Date: Mon, 4 Oct 2010 08:51:08 -0500
Message-ID: <AANLkTiks0ap9mwN6nN3679oYgyEDfMwhmReyR5=gUJvH@mail.gmail.com>
Subject: Re: A proposed use case, any comments and experience is appreciated
From: Jonathan Ellis <jbellis@gmail.com>
To: user <user@cassandra.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Expiring columns are 0.7 only.

An expired column behaves like a deleted column until it is compacted away.

On Mon, Oct 4, 2010 at 8:48 AM, Utku Can Top=E7u <utku@topcu.gen.tr> wrote:
> Hi Jonathan,
>
> Thank you for mentioning about the expiring columns issue. I didn't know
> that it had existed.
> That's really great news.
> First of all, does the current 0.6 branch support it? If not so, is the
> patch available for the 0.6.5 somehow?
> And about the deletion issue, if all the columns in a row expire? When th=
e
> row will be deleted, will I be seeing the row in my map inputs somehow, a=
nd
> for how long?
>
> Regards,
> Utku
>
> On Mon, Oct 4, 2010 at 3:30 PM, Jonathan Ellis <jbellis@gmail.com> wrote:
>>
>> A simpler approach might be to insert expiring columns into a 2nd CF
>> with a TTL of one hour.
>>
>> On Mon, Oct 4, 2010 at 5:12 AM, Utku Can Top=E7u <utku@topcu.gen.tr> wro=
te:
>> > Hey All,
>> >
>> > I'm planning to run Map/Reduce on one of the ColumnFamilies. The keys
>> > are
>> > formed in such a fashion that, they are indexed in descending order by
>> > time.
>> > So I'll be analyzing the data for every hour iteratively.
>> >
>> > Since the current Hadoop integration does not support partial
>> > columnfamily
>> > analysis. I feel that, I'll need to dump the data of the last hour and
>> > put
>> > it to the hadoop cluster and do my analysis on the flat text file.
>> > Do you think of any other "better" way of getting the data of a keyran=
ge
>> > into a hadoop cluster for analysis?
>> >
>> > Regards,
>> >
>> > Utku
>> >
>> >
>> >
>>
>>
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of Riptano, the source for professional Cassandra support
>> http://riptano.com
>
>


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com