Hi, No, the keys are hashed to be distributed, at least if you use RandomPartitioner.From http://www.datastax.com/docs/1.0/cluster_architecture/partitioning:"To distribute the data evenly across the number of nodes, a hashing algorithm creates an MD5 hash value of the row key" .vegard,
----- Original Message ----- From: [email protected] To: Cc: Sent:Tue, 22 Jan 2013 09:40:19 -0200 Subject:Re: How to store large columns? But, this keys have the same prefix. So, they will be distributed on the same node Right? 2013/1/21 Jason Brown The reason for multiple keys (and, by extension, multiple columns) is to better distribute the write/read load across the cluster as keys will (hopefully) be distributed on different nodes. This helps to avoid hot spots. Hope this helps, -Jason Brown Netflix ------------------------- FROM: Sávio Teles [[email protected] [2]] SENT: Monday, January 21, 2013 9:51 AM TO: [email protected] [3] SUBJECT: Re: How to store large columns? Astyanax split large objects into multiple keys. Is it a good idea? It is better to split into multiple columns? Thanks 2013/1/21 Sávio Teles Thanks Keith Wright. 2013/1/21 Keith Wright This may be helpful: https://github.com/Netflix/astyanax/wiki/Chunked-Object-Store [6] From: Vegard Berget Reply-To: "[email protected] [8]" , Vegard Berget Date: Monday, January 21, 2013 8:35 AM To: "[email protected] [11]" Subject: Re: How to store large columns? Hi, You could split it into multiple columns on the client side: RowKeyData: Part1: [1mb], Part2: [1mb], Part3: [1mb]...PartN[1mb] Now you can use multiple get() in parallell to get the files back and then join them back to one file. I _think_ maybe the new CQL3-protocol does not have the same limitation, but I have never tried large columns there, so someone with more experience than me will have to confirm this. .vegard, ----- Original Message ----- From: [email protected] [13] To: Cc: Sent: Mon, 21 Jan 2013 11:16:40 -0200 Subject: How to store large columns? We wish to store a column in a row with size larger than thrift_framed_transport_size_in_mb. But, Thrift has a maximum frame size configured by thrift_framed_transport_size_in_mb in cassandra.yaml. so, How to store columns with size larger than thrift_framed_transport_size_in_mb? Increasing this value does not solve the problem, since we have columns with varying sizes. -- Atenciosamente, Sávio S. Teles de Oliveira voice: +55 62 9136 6996 http://br.linkedin.com/in/savioteles [15] Mestrando em Ciências da Computação - UFG Arquiteto de Software Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG -- Atenciosamente, Sávio S. Teles de Oliveira voice: +55 62 9136 6996 http://br.linkedin.com/in/savioteles [16] Mestrando em Ciências da Computação - UFG Arquiteto de Software Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG -- Atenciosamente, Sávio S. Teles de Oliveira voice: +55 62 9136 6996 http://br.linkedin.com/in/savioteles [17] Mestrando em Ciências da Computação - UFG Arquiteto de Software Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG -- Atenciosamente, Sávio S. Teles de Oliveira voice: +55 62 9136 6996 http://br.linkedin.com/in/savioteles [18] Mestrando em Ciências da Computação - UFG Arquiteto de Software Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG Links: ------ [1] mailto:[email protected] [2] mailto:[email protected] [3] mailto:[email protected] [4] mailto:[email protected] [5] mailto:[email protected] [6] https://github.com/Netflix/astyanax/wiki/Chunked-Object-Store [7] mailto:[email protected] [8] mailto:[email protected] [9] mailto:[email protected] [10] mailto:[email protected] [11] mailto:[email protected] [12] mailto:[email protected] [13] mailto:[email protected] [14] mailto:[email protected] [15] http://br.linkedin.com/in/savioteles [16] http://br.linkedin.com/in/savioteles [17] http://br.linkedin.com/in/savioteles [18] http://br.linkedin.com/in/savioteles
