he
>> mapred.job.reuse.jvm.num.tasks property), and MultiFileInputSplit which
>> can run more than one split per map.
>>
>> -Original Message-
>> From: Hiller, Dean [mailto:dean.hil...@nrel.gov]
>> Sent: 04 March 2013 13:38
>> To: user@cassandra.
overhead: task JVM reuse for running multiple map tasks in one JVM,
>thereby avoiding some JVM startup overhead (see the
>mapred.job.reuse.jvm.num.tasks property), and MultiFileInputSplit which
>can run more than one split per map.
>
>-Original Message-
>From: Hiller, Dean
an run more than one split per map.
-Original Message-
From: Hiller, Dean [mailto:dean.hil...@nrel.gov]
Sent: 04 March 2013 13:38
To: user@cassandra.apache.org
Subject: Re: Storage question
Well, astyanax I know can simulate streaming into cassandra and disperses the
file to multiple rows i
Each storage system has its own purpose. While Cassandra would be good
for metadata, depending on the size of objects Cassandra could be not
the best fit. You need something more like Amazon S3 for blob storage.
Try Ceph RADOS or OpenStack Object Store which both provide S3
compatible API.
On
March 4, 2013 12:34 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Storage question
Hi – Can someone suggest the optimal way to store files / images ? We are
planning to use cassandra for meta-data for these files.
.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Storage question
Hi – Can someone suggest the optimal way to store files / images ? We are
planning to use cassandra for meta-data for these files. HDFS is not good for
small file size .. can we
look at something else ?
Thank
Hi - Can someone suggest the optimal way to store files / images ? We are
planning to use cassandra for meta-data for these files. HDFS is not good for
small file size .. can we
look at something else ?
Thanks,
Kanwar
