Is Cassandra suitable for this use case?

hi, all - I am very new to Cassandra, please bear with me if this is really a FAQ. We are exploring if Cassandra is suitable use for a data management project. The basic characteristics of the data are the following: - it centers around data files, each data file's size can be very small to very

Re: Is Cassandra suitable for this use case?

hi Evgeny I appreciate the input. The concern with HDFS is that it has own share of problems - its name node, which essentially a metadata server, load all files information into memory (roughly 300 MB per million files) and its failure handling is far less attractive ... on top of configuring an

Re: Is Cassandra suitable for this use case?

hi Sasha - Yes indeed. this solution was in the second part of my original question - it just seems "out of norm" on what people usually use Cassandra for, I guess I am looking for some reassurance before I roll up the sleeve of trying it. Thanks Ruby On Thu, Aug 25, 2011 at 12:36 PM, Sasha Dol

Re: Is Cassandra suitable for this use case?

ache.org > Sent: Thursday, August 25, 2011 12:36:21 PM > Subject: Re: Is Cassandra suitable for this use case? > > You can chunk the files into pieces and store the pieces in Cassandra... > Munge all the pieces back together when delivering back to the client... > > On Aug

UUID cli output

hi all I am using UUID as my row key, and when examine it in CLI, I was expecting something like this that get printed: b2f0da40-ec2c-11e0--242d50cf1fbf instead, I am seeing something like this: 633866363838343065626462313165303030303032343264353063663166 How does this get transformed?