Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of simonmetson@googlemail.com
 designates 74.125.82.180 as permitted sender)
Date: Fri, 3 Feb 2012 21:21:41 +0000
From: Simon Metson <simonmetson@googlemail.com>
To: user@couchdb.apache.org
Message-ID: <C5EE5BC0ABCE4A938876FE0F81690DE3@googlemail.com>
In-Reply-To: 
 <7D9AF4B98807C54EBADEA75DF6D5ACB701588E870B@NDA-HCLC-EVS04.HCLC.CORP.HCL.IN>
References: 
 <7D9AF4B98807C54EBADEA75DF6D5ACB701588E870B@NDA-HCLC-EVS04.HCLC.CORP.HCL.IN>
Subject: Re: CouchDB with HDFS
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4f2c4fe5_3a95f874_4dc0"

--4f2c4fe5_3a95f874_4dc0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi, 
No you can't really do that. You could set up FUSE to access HDFS and then write into the FUSE mount from Couch but that'd be slow. If you need a cluster you'd be better off using BigCouch.
Cheers
Simon


On Friday, 3 February 2012 at 12:46, Stuti Awasthi wrote:

> Hi all,
> I am a newbee for couchDb and using HDFS for quiet some time now. I wanted to know that can I integrate CouchDB and HDFS together.
> By integration I mean, I can use CouchDB as a database and filesystem can be HDFS.
> 
> Please suggest.
> 
> Thanks
> Stuti
> 
> ::DISCLAIMER::
> -----------------------------------------------------------------------------------------------------------------------
> 
> The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
> It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
> this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
> Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
> this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
> received this email in error please delete it and notify the sender immediately. Before opening any mail and
> attachments please check them for viruses and defect.
> 
> ----------------------------------------------------------------------------------------------------------------------- 


--4f2c4fe5_3a95f874_4dc0--