Hi Shalom, You might want to compress on application side before inserting in Cassandra, using the algorithm on your choice, based on compression ratio and speed that you found acceptable with your use case
On 4 April 2018 at 14:38, shalom sagges <shalomsag...@gmail.com> wrote: > Thanks DuyHai! > > I'm using the default table compression. Is there anything else I should > look into? > Regarding the table compression, I understand that for write heavy tables, > it's best to keep the default and not compress it further. Have I > understood correctly? > > On Wed, Apr 4, 2018 at 3:28 PM, DuyHai Doan <doanduy...@gmail.com> wrote: > >> Compress it and stores it as a blob. >> Unless you ever need to index it but I guess even with SASI indexing a so >> huge text block is not a good idea >> >> On Wed, Apr 4, 2018 at 2:25 PM, shalom sagges <shalomsag...@gmail.com> >> wrote: >> >>> Hi All, >>> >>> A certain application is writing ~55,000 characters for a single row. >>> Most of these characters are entered to one column with "text" data type. >>> >>> This looks insanely large for one row. >>> Would you suggest to change the data type from "text" to BLOB or any >>> other option that might fit this scenario? >>> >>> Thanks! >>> >> >> >
