Best practice to store large keys (= 64 KByte)

Hi Cassandra users, I'm wondering if there are any best practices to use keys (= 64 KByte). I'm aware that there is a Cassandra restriction for this [1]. However, my application requires that some keys may be = 64 KByte. I'm currently trying a simple hash-table solution: //key BLOB may be =

Re: Deleting column names

:51 PM, Eric Plowe eric.pl...@gmail.com mailto:eric.pl...@gmail.com wrote: Also I don't think you can null out columns that are part of the primary key after they've been set. On Monday, April 21, 2014, Andreas Wagner andreas.josef.wag

Re: Deleting column names

Hi cassandra users, hi Sebastian, I'd be interested in this ... is there any update/solution? Thanks so much ;) Andreas On 04/16/2014 11:43 AM, Sebastian Schmidt wrote: Hi, I'm using a Cassandra table to store some data. I created the table like this: CREATE TABLE IF NOT EXISTS table_name (s

Re: Uneven CPU load on a 4 node cluster

Hi all, I'm experiencing very similar effects. Did you (or anyone for that matter) have/solvethis issue? I have a 3 node cluster with vnodes having the same #tokens (256). Infact, all nodes are configured identical and share similar/same hardware. Cassandra.yaml settings are fairly standard