Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 38828 invoked from network); 8 Mar 2011 06:12:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Mar 2011 06:12:35 -0000 Received: (qmail 6491 invoked by uid 500); 8 Mar 2011 06:12:33 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 6324 invoked by uid 500); 8 Mar 2011 06:12:32 -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 6314 invoked by uid 99); 8 Mar 2011 06:12:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 06:12:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of adynnn@gmail.com designates 209.85.212.172 as permitted sender) Received: from [209.85.212.172] (HELO mail-px0-f172.google.com) (209.85.212.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Mar 2011 06:12:24 +0000 Received: by pxi6 with SMTP id 6so1338108pxi.31 for ; Mon, 07 Mar 2011 22:12:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=9LwBER+50ulbASAERTYQpwm+HLUhDT8ckVHLb+HKWqk=; b=JZH7GAqgo44x0/oJSMZC+pNetQRFUEbmOz6F4hMhr/b0cKzEOt6blhykQXKpakiel4 jf7jOJ9IB7GCuf9KKyZM6ey2QgNw0loHEXn3F/V6Em5inMGDEJQiAEFVzi7p2oR3xTqJ oh8bo9brSox/ya0Sqfiv5rIAjwlOwpKYZyKmI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=o42m5YcoW+RkGGXynCVFhatOQfSxb7slioCrkyqy1nq6E27r3R3YNEJhB6eKLxEs8H 0/xDm3FDW4nn5rD4ZLHp91XRxOiwK4SbGbr9FzE50KJU6UjrqKyaO0KGgV3nh6NIVtXl CHrtG0PqU1OAqXtUjwrHYosO757uEIRx6wsbg= MIME-Version: 1.0 Received: by 10.142.201.12 with SMTP id y12mr4042132wff.215.1299564723146; Mon, 07 Mar 2011 22:12:03 -0800 (PST) Received: by 10.142.199.4 with HTTP; Mon, 7 Mar 2011 22:12:03 -0800 (PST) Date: Tue, 8 Mar 2011 11:42:03 +0530 Message-ID: Subject: Splitting the data of a single blog into 2 CFs (to implement effective caching) according to views. From: Aditya Narayan To: user Content-Type: multipart/alternative; boundary=000e0cd32ef8af9022049df27d67 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd32ef8af9022049df27d67 Content-Type: text/plain; charset=ISO-8859-1 My application displays list of several blogs' overview data (like blogTitle/ nameOfBlogger/ shortDescrption for each blog) on 1st page (in very much similar manner like Digg's newsfeed) and when the user selects a particular blog to see., the application takes him to that specific blog's full page view which displays entire data of the blog. Thus I am trying to split a blog's data in *two rows*, in two **different CFs ** (one CF is row-cached(with less amount of data in each row) and another(with each row having entire remaining blog data) without caching). Data for 1st page view (like titles and other overview data of a blog) are put in a row in 1st CF. This CF is cached so as to improve the performance of heavily read data. Only the data from cached CF is read for 1st page. The other remaining data(bulk amount of text of blog and entire comments data) are stored as another row in 2nd CF. For 2nd page, **rows from both of the two CFs have to be read**. This will take two read operations. Does this seem to be a good design ? --000e0cd32ef8af9022049df27d67 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
My application=A0 displays list of several blogs' overview data (li= ke blogTitle/ nameOfBlogger/ shortDescrption for each blog) on 1st page (in= very much similar manner like Digg's newsfeed) and when the user selec= ts a particular blog to see., the application takes him to that specific bl= og's full page view which displays entire data of the blog.

Thus I am trying to split a blog's data in *two rows*, in two **dif= ferent CFs ** (one CF is row-cached(with less amount of data in each row) a= nd another(with each row having entire remaining blog data) without caching= ).

Data for 1st page view (like titles and other overview data of a blog) = are put in a row in 1st CF. This CF is cached so as to improve the performa= nce of heavily read data. Only the data from cached CF is read for 1st page= . The other remaining data(bulk amount of text of blog and entire comments = data)=A0 are stored as another row in 2nd CF. For 2nd page, **rows from bot= h of the two CFs have to be read**. This will take two read operations.

Does this seem to be a good design ?
--000e0cd32ef8af9022049df27d67--