incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Hobbs <ty...@datastax.com>
Subject Re: rolling window of data
Date Thu, 03 Feb 2011 06:12:41 GMT
No, Logsandra does not use a rolling window.

The correct way to accomplish what you describe is the new (in 0.7)
per-column TTL.  Simply set this to 60 * 60 * 24 * 90 (90 day's worth of
seconds) and your columns will magically disappear after that length of
time.

- Tyler

On Wed, Feb 2, 2011 at 11:46 PM, Jeffrey Wang <jwang@palantir.com> wrote:

> Thanks for the link, but unfortunately it doesn’t look like it uses a
> rolling window. As far as I can tell, log entries just keep getting inserted
> into Cassandra.
>
>
>
> -Jeffrey
>
>
>
> *From:* Aaron Morton [mailto:aaron@thelastpickle.com]
> *Sent:* Wednesday, February 02, 2011 9:21 PM
> *To:* user@cassandra.apache.org
> *Subject:* Re: rolling window of data
>
>
>
> This project may provide some inspiration for you
> https://github.com/thobbs/logsandra
>
>
>
> Not sure if it has a rolling window, if you find out let me know :)
>
>
>
> Aaron
>
>
>
> On 03 Feb, 2011,at 06:08 PM, Jeffrey Wang <jwang@palantir.com> wrote:
>
> Hi,
>
>
>
> We’re trying to use Cassandra 0.7 to store a rolling window of log data
> (e.g. last 90 days). We use the timestamp of the log entries as the column
> names so we can do time range queries. Everything seems to be working fine,
> but it’s not clear if there is an efficient way to delete data that is more
> than 90 days old.
>
>
>
> Originally I thought that using a slice range on a deletion would do the
> trick, but that apparently is not supported yet. Another idea I had was to
> store the timestamp of the log entry as Cassandra’s timestamp and pass in
> artificial timestamps to remove (thrift API), but that seems hacky. Does
> anyone know if there is a good way to support this kind of rolling window of
> data efficiently? Thanks.
>
>
>
> -Jeffrey
>
>
>
>

Mime
View raw message