But, this keys have the same prefix. So, they will be distributed on the same node. Right?
2013/1/21 Jason Brown <jasbr...@netflix.com> > 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 [savio.te...@lupa.inf.ufg.br] > *Sent:* Monday, January 21, 2013 9:51 AM > *To:* user@cassandra.apache.org > > *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 <savio.te...@lupa.inf.ufg.br> > >> >> Thanks Keith Wright. >> >> >> 2013/1/21 Keith Wright <kwri...@nanigans.com> >> >>> This may be helpful: >>> https://github.com/Netflix/astyanax/wiki/Chunked-Object-Store >>> >>> From: Vegard Berget <p...@fantasista.no> >>> Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org>, >>> Vegard Berget <p...@fantasista.no> >>> Date: Monday, January 21, 2013 8:35 AM >>> To: "user@cassandra.apache.org" <user@cassandra.apache.org> >>> 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: >>> user@cassandra.apache.org >>> >>> To: >>> <user@cassandra.apache.org> >>> 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 >>> thanthrift_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 >>> 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 >> 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 > 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 Mestrando em Ciências da Computação - UFG Arquiteto de Software Laboratory for Ubiquitous and Pervasive Applications (LUPA) - UFG
