why not just store the URL of pic / video, just like the RDBMS did, cassandra is merely a distributed database from some kind point of view. it is more like a schema design issue. Any video or pic should not be put into the DB especially big data table DB as raw binary format. and did this kind of thing gonna cause the performance issue afterward, since it is against the original design of cassandra.
On Wed, Jun 20, 2012 at 2:22 PM, Paolo Bernardi <berna...@gmail.com> wrote: > Take also into account Thrift's limits. > > http://wiki.apache.org/cassandra/CassandraLimitations > > Paolo > On Jun 20, 2012 10:11 PM, "Dave Brosius" <dbros...@mebigfatguy.com> wrote: > >> >> Column values are limited at 2G. >> >> Why store them as Base64? that just adds overhead. Storing the raw bytes >> will save you a bunch. >> >> >> *----- Original Message -----* >> *From:* "Cyril Auburtin" <cyril.aubur...@gmail.com> >> *Sent:* Wed, June 20, 2012 13:38 >> *Subject:* store large String as col value >> >> In order to store picture, transfered as a base 64 encoded String in the >> message >> >> I wanted to ask, what is the limit for column values (since the wiki is >> down just now) >> >> the row has a limit of 2GB, it should be enough for pictures, but a >> single column Row, has als o a limit of ~2GB? >> >> Is it critical with replication? Is it better to cut down the String in >> shorter pieces and store them in different rows to support more easily >> read/write towards replication? >> >
