Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Mon, 29 Mar 2010 20:35:46 -0000
Message-ID: <20100329203546.13070.27435@eos.apache.org>
Subject: =?utf-8?q?=5BCassandra_Wiki=5D_Update_of_=22FAQ=22_by_Nick_Pavlica?=

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for=
 change notification.

The "FAQ" page has been changed by Nick Pavlica.
http://wiki.apache.org/cassandra/FAQ?action=3Ddiff&rev1=3D45&rev2=3D46

--------------------------------------------------

  =

  These notes were taken from the Cassandra limitations section (http://wik=
i.apache.org/cassandra/CassandraLimitations):
  ----
+ =

+ [CassandraLimitiations]
+ =

+ =

  * Cassandra's public API is based on Thrift, which offers no streaming ab=
ilities -- any value written or fetched has to fit in memory.  This is inhe=
rent to Thrift's design; I don't see it changing.  So adding large object s=
upport to Cassandra would need a special API that manually split the large =
objects up into pieces.  Jonathan Ellis sketched out one approach in http:/=
/issues.apache.org/jira/browse/CASSANDRA-265.  As a workaround in the meant=
ime, you can manually split files into chunks of whatever size you are comf=
ortable with -- at least one person is using 64MB -- and making a file corr=
espond to a row, with the chunks as column values.
 =20