Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4E02B5B8.1000009@surfworx.com>
Date: Wed, 22 Jun 2011 20:40:40 -0700
From: Don Ledford <don.ledford@surfworx.com>
Reply-To: don.ledford@surfworx.com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Storing files in blob into Cassandra
References: <BANLkTikWpc-oTfxwHXp6mnKrnRhtnzA+JA@mail.gmail.com>
	<BANLkTinmmdKEGFW+H1dZ9Kr6WxhO6Js_HA@mail.gmail.com>
	<BANLkTimZz72Tf3n5W9i9Bf=5R5PjZchmfw@mail.gmail.com>
 <BANLkTi=X_f1MBwei=UzoSFXVcop1PUtRWA@mail.gmail.com>
In-Reply-To: <BANLkTi=X_f1MBwei=UzoSFXVcop1PUtRWA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 06/22/2011 01:23 AM, Damien Picard wrote:
>  >store your images / documents / etc. somewhere and reference them
>  >in Cassandra.  That's the consensus that's been bandied about on this
>  >list quite frequently

I store large files in Cassandra using columns for file blocks.   I have 
a simple blob class over the top of this which handles input and output 
streaming so reads/writes are only one column at a time. I don't have 
time to post the details, but it's pretty simple - each blob has it's 
own key and it's blocks are the columns. Column names are essentially 
the block number.

I prefer this since there's no need to deal with yet another disk store 
and it's associated security, redundancy, and cost.

- Don