Hello, Have you looked at solving this challenge with clustering columns? Also, please describe the problem set details for more specific advice from this group.
Starting new projects on Thrift isn't the recommended approach. Jonathan [image: datastax_logo.png] Jonathan Lacefield Solution Architect | (404) 822 3487 | jlacefi...@datastax.com [image: linkedin.png] <http://www.linkedin.com/in/jlacefield/> [image: facebook.png] <https://www.facebook.com/datastax> [image: twitter.png] <https://twitter.com/datastax> [image: g+.png] <https://plus.google.com/+Datastax/about> <http://feeds.feedburner.com/datastax> <https://github.com/datastax/> On Tue, Jan 20, 2015 at 1:24 PM, chetan verma <chetanverm...@gmail.com> wrote: > Hi, > > I am starting a new project with cassandra as database. > I have unstructured data so I need dynamic columns, > though in CQL3 we can achive this via Collections but there are some > downsides to it. > 1. Collections are used to store small amount of data. > 2. The maximum size of an item in a collection is 64K. > 3. Cassandra reads a collection in its entirety. > 4. Restrictions on number of items in collections is 64,000 > > And no support to get single column by map key, which is possible via > cassandra cli. > Please suggest whether I should use CQL3 or Thrift and which driver is > best. > > -- > *Regards,* > *Chetan Verma* > *+91 99860 86634 <%2B91%2099860%2086634>* >
