Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 78068 invoked from network); 2 Mar 2011 08:23:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Mar 2011 08:23:52 -0000 Received: (qmail 1990 invoked by uid 500); 2 Mar 2011 08:23:50 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 1743 invoked by uid 500); 2 Mar 2011 08:23:46 -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 1735 invoked by uid 99); 2 Mar 2011 08:23:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 08:23:46 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sdolgy@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qy0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Mar 2011 08:23:38 +0000 Received: by qyk7 with SMTP id 7so4595980qyk.10 for ; Wed, 02 Mar 2011 00:23:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=1xhNgQjzqHai2pX+Q/XdkADwsPtApl8lnpexsZDtWAI=; b=ujCphVZHjJqzszkeQLDgDRAQ1NeaRwJVQ9mRbyX56+dpVOlfI5CuO7EDqh+0EiqFe6 M7OEKoq/fRfz08//B1PJK1Tz5ndrH/GIR4haK31NsZQxCoAFqYpxx4MJg6CR23qA9AEH vb5Nuadkeew9x2gngXmtSBQgzWliBRlLwU1Ys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=WlnOSoCMSUJqqkJpBLe0IM0BRJI7vd789YZoS1h1mKkcbYY1I6aEzTcZ+2t0EepKb+ l6HBaB/XlDWSUV9Iye4mQIBgzP1i2Yv3L+QhYJK28xBL2J8W1ZEAxJgeaOtnLmpBPQO9 5ufpcUN4rySj2+EWmLDTb2AjqQdnzMTzpuZtc= Received: by 10.224.53.200 with SMTP id n8mr6757919qag.226.1299054197155; Wed, 02 Mar 2011 00:23:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.229.239.7 with HTTP; Wed, 2 Mar 2011 00:22:57 -0800 (PST) In-Reply-To: References: <1299005018456-6078278.post@n2.nabble.com> From: Sasha Dolgy Date: Wed, 2 Mar 2011 09:22:57 +0100 Message-ID: Subject: Re: Storing photos, images, docs etc. To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I took the advice from previous threads and use cassandra to hold pointers to the files that are uploaded and other meta information. Amazon S3 can be quite simple and pain free at times and was a great cost-effective place for me to keep the large files... i have had some great success already with this approach and read/serve the data from the large files only when they are required -sd On Tue, Mar 1, 2011 at 8:44 PM, Edward Capriolo wrote: > On Tue, Mar 1, 2011 at 1:43 PM, mcasandra wrote: >> Is it advisable or ok to store photos, images and docs in cassandra where you >> expect high volume of uploads and views? >> >> I was reading about facebook implementation of haystack to store the photos. >> They don't put anything in their mysql db. >> >> Since Cassandra is different from mysql I was wondering if it's ok or if >> there are going to be any issues. >> >> I tried searching online to read articles or papers on similar subject but >> couldn't find any where cassandra was being used to store docs/images etc.