S3 is a file storage service. It does provide versioning and key based file
access, but it does not provide any processing paradigm, like Map Reduce
for Hadoop. HBase provides random access to data - its more like a database
in that you can have a key based access for records, and it is a columnar
store. S3 can be compared with HDFS, the hadoop distributed file system,
and in fact one can spin Hadoop clusters off S3 file system.
Maybe if you explain your problem in detail, we can help you further on the
mailing list. You can also read up the fundamentals on the Hadoop and HBase
wiki, there is a high level introduction which can clear the basic doubts.
Hope that helps.
Crux: Reporting for HBase <https://github.com/sonalgoyal/crux>
Nube Technologies <http://www.nubetech.co>
On Fri, Nov 25, 2011 at 7:10 AM, Aditya Kumar <[EMAIL PROTECTED]>wrote:
> Thanks Li Pi.
> does it mean that s3 is hadoop?
> can you please let me know what I will be missing if I use s3 only with
> out Hbase?
> 2) In s3 there is delete operation, does it really delete the key and
> there by value?
> From: Li Pi <[EMAIL PROTECTED]>
> To: Aditya Kumar <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
> Sent: Thursday, November 24, 2011 5:29 PM
> Subject: Re: Amazon s3 and Hadoop/Hbase
> You can run hbase against s3.
> On Nov 24, 2011 5:11 PM, "Aditya Kumar" <[EMAIL PROTECTED]> wrote:
> > Hi,
> > I am looking at Amazon S3.
> > is it like HDFS/Hadoop? .
> > If it is like Hadoop can we add only data to the tables.. than can we use
> > Hbase?
> > I tried to read online,
> > all I see that S3 will not delete the data and will do versioing
> > (something similar to Hadoop)
> > TIA,
> > Adi