You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by Apache Wiki <wi...@apache.org> on 2010/03/29 22:19:52 UTC

[Cassandra Wiki] Update of "FAQ" 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=diff&rev1=44&rev2=45

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

   * [[#cloned|Why does nodeprobe ring only show one entry, even though my nodes logged that they see each other joining the ring?]]
   * [[#range_ghosts|Why do deleted keys show up during range scans?]]
   * [[#change_replication|Can I change the ReplicationFactor on a live cluster?]]
+  * [[#large_file_and_blob_storage|Can I store large files or BLOBs in Cassandra?]]
+ 
  
  <<Anchor(cant_listen_on_ip_any)>>
  == Why can't I make Cassandra listen on 0.0.0.0 (all my addresses)? ==
@@ -200, +202 @@

  If you're increasing the ReplicationFactor:
   * Run "nodetool repair" to run an anti-entropy repair on the cluster. This is an intensive process so may result in adverse cluster performance.
  
+ <<Anchor(large_file_and_blob_storage)>>
+ == Can I Store BLOBs in Cassandra? ==
+ Currently Cassandra isn't optimized specifically for large file or BLOB storage, however there are ways to work around this.
+ 
+ These notes were taken from the Cassandra limitations section (http://wiki.apache.org/cassandra/CassandraLimitations):
+ ----
+ * Cassandra's public API is based on Thrift, which offers no streaming abilities -- any value written or fetched has to fit in memory.  This is inherent to Thrift's design; I don't see it changing.  So adding large object support 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 meantime, you can manually split files into chunks of whatever size you are comfortable with -- at least one person is using 64MB -- and making a file correspond to a row, with the chunks as column values.
+