That's correct.
On Wed, Feb 3, 2010 at 4:49 PM, Michael Pearson wrote:
> Thanks for the Gossip note, I'll keep reading up on the protocols.
> For key/column/disk I meant in terms of the Cassandra limitation -
>
> "The main limitation on column and supercolumn size is that all data
> for a single
Thanks for the Gossip note, I'll keep reading up on the protocols.
For key/column/disk I meant in terms of the Cassandra limitation -
"The main limitation on column and supercolumn size is that all data
for a single key and column must fit (on disk) on a single machine in
the cluster."
Is it righ
On Wed, Feb 3, 2010 at 4:25 PM, Michael Pearson wrote:
> I'd imagine the gossip overhead and key/column per disk limitation is
> too open for abuse to recommend storing lob columns with any level of
> predictability, particularly if frequent updates are involved.
Gossip overhead is constant for a
I'd imagine the gossip overhead and key/column per disk limitation is
too open for abuse to recommend storing lob columns with any level of
predictability, particularly if frequent updates are involved. Would
you say it's generally better form to store manifests or file pointers
only, and send the
At least one person is putting in chunks of up to 64MB, so at some
level it "works" but it's not what it's designed for.
2010/2/3 Ted Zlatanov :
> On Tue, 2 Feb 2010 23:05:04 -0600 Jonathan Ellis wrote:
>
> JE> The "atom" in cassandra is a single column. These are almost always
> JE> under 1KB.
On Tue, 2 Feb 2010 23:05:04 -0600 Jonathan Ellis wrote:
JE> The "atom" in cassandra is a single column. These are almost always
JE> under 1KB.
Is there any point to storing large objects (over 100MB) in Cassandra
columns? I'm considering it but it seems like a bad idea based on my
reading of
On Tue, Feb 2, 2010 at 9:05 PM, Anthony Di Franco
wrote:
> Taking the discussion below to the dev list.
>
> Continuing the discussion, it seems to me that objects in Cassandra
> might be quite large from this passage:
You've misunderstood. The "atom" in cassandra is a single column.
These are al
ic online code for efficient redundancy (or specify why this is
> not appropriate for Cassandra in the documentation). Systematic online codes
> permit an arbitrarily large or small number of repair symbols to be added to
> the original data to more smoothly increase the amount of redundant s
