Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C92717EA7 for ; Thu, 23 Apr 2015 17:09:14 +0000 (UTC) Received: (qmail 50465 invoked by uid 500); 23 Apr 2015 17:09:03 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 50418 invoked by uid 500); 23 Apr 2015 17:09:03 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 50408 invoked by uid 99); 23 Apr 2015 17:09:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Apr 2015 17:09:03 +0000 X-ASF-Spam-Status: No, hits=3.4 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of ali.rac200@gmail.com does not designate 54.76.25.247 as permitted sender) Received: from [54.76.25.247] (HELO mx1-eu-west.apache.org) (54.76.25.247) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Apr 2015 17:08:36 +0000 Received: from mail-qg0-f44.google.com (mail-qg0-f44.google.com [209.85.192.44]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 9240826211 for ; Thu, 23 Apr 2015 16:45:04 +0000 (UTC) Received: by qgeb100 with SMTP id b100so10799875qge.3 for ; Thu, 23 Apr 2015 09:45:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=B9tet3Rinux23cQMVZYWjHiiAKn0N/rk7ouLt7BukqE=; b=Yut7Du9JK5M6bYWXd1m64aY4ivRmAWauA7hqmyRRMoU+Ang4yRnYPvYlm5654b/+nZ 1TzY1ApeDGI7ej81QC44E30w/RTP6aIXH3O8oiGOoCZXXsrNgrxhV2Kc6/4abRJQkxG4 6VyZSSwsdBGm6HZHKeqEOnx5gPqEJsnBN8LPDAXA1iKAfE6ejIW+L3iQemT/rpdD8lm4 WwtBtdiXoA6v24T7E2v1ekjNn+XDoJoVr6xe+fB19448n0kdR/CKKi31KMW65C5xIRez R116phldmujr3udhTSm22QESU4lfD+qI9YTVd+yMYGBbD+bk5oAX7kTLFmicFpm84BMU dZ4w== MIME-Version: 1.0 X-Received: by 10.55.22.222 with SMTP id 91mr6938142qkw.101.1429807503170; Thu, 23 Apr 2015 09:45:03 -0700 (PDT) Received: by 10.140.29.225 with HTTP; Thu, 23 Apr 2015 09:45:03 -0700 (PDT) In-Reply-To: References: Date: Thu, 23 Apr 2015 21:45:03 +0500 Message-ID: Subject: Re: Data model suggestions From: Ali Akhtar To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a1149572452e282051467007a X-Virus-Checked: Checked by ClamAV on apache.org --001a1149572452e282051467007a Content-Type: text/plain; charset=UTF-8 That's returned by the external API we're querying. We query them for active records, if a previous active record isn't included in the results, that means its time to archive that record. On Thu, Apr 23, 2015 at 9:20 PM, Manoj Khangaonkar wrote: > Hi, > > How do you determine if the record is no longer active ? Is it a perioidic > process that goes through every record and checks when the last update > happened ? > > regards > > On Thu, Apr 23, 2015 at 8:09 AM, Ali Akhtar wrote: > >> Hey all, >> >> We are working on moving a mysql based application to Cassandra. >> >> The workflow in mysql is this: We have two tables: active and archive . >> Every hour, we pull in data from an external API. The records which are >> active, are kept in 'active' table. Once a record is no longer active, its >> deleted from 'active' and re-inserted into 'archive' >> >> The purpose for that, is because most of the time, queries are only done >> against the active records rather than archived. Therefore keeping the >> active table small may help with faster queries, if it only has to search >> 200k records vs 3 million or more. >> >> Is it advisable to keep the same data model in Cassandra? I'm concerned >> about tombstone issues when records are deleted from active. >> >> Thanks. >> > > > > -- > http://khangaonkar.blogspot.com/ > --001a1149572452e282051467007a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
That's returned by the external API we're querying= . We query them for active records, if a previous active record isn't i= ncluded in the results, that means its time to archive that record.

On Thu, Apr 23, 201= 5 at 9:20 PM, Manoj Khangaonkar <khangaonkar@gmail.com> = wrote:
Hi,
=
How do you determine if the record is no longer active ? Is it a = perioidic process that goes through every record and checks when the last u= pdate happened ?

regards
<= div>

On Thu, Apr 23, 2015 a= t 8:09 AM, Ali Akhtar <ali.rac200@gmail.com> wrote:
Hey all,

W= e are working on moving a mysql based application to Cassandra.
<= br>
The workflow in mysql is this: We have two tables: active and= archive . Every hour, we pull in data from an external API. The records wh= ich are active, are kept in 'active' table. Once a record is no lon= ger active, its deleted from 'active' and re-inserted into 'arc= hive'

The purpose for that, is because most of= the time, queries are only done against the active records rather than arc= hived. Therefore keeping the active table small may help with faster querie= s, if it only has to search 200k records vs 3 million or more.
Is it advisable to keep the same data model in Cassandra? I= 9;m concerned about tombstone issues when records are deleted from active.= =C2=A0

Thanks.



--

--001a1149572452e282051467007a--