Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3B898D876 for ; Fri, 15 Feb 2013 18:28:47 +0000 (UTC) Received: (qmail 76694 invoked by uid 500); 15 Feb 2013 18:28:43 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 76588 invoked by uid 500); 15 Feb 2013 18:28:43 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 76578 invoked by uid 99); 15 Feb 2013 18:28:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2013 18:28:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mlortiz@uci.cu designates 200.55.140.180 as permitted sender) Received: from [200.55.140.180] (HELO mx3.uci.cu) (200.55.140.180) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 15 Feb 2013 18:28:38 +0000 Received: (qmail 31668 invoked by uid 507); 15 Feb 2013 18:28:15 -0000 Received: from 10.0.0.185 by ns3.uci.cu (envelope-from , uid 501) with qmail-scanner-2.01st (avp: 5.0.2.0. spamassassin: 3.0.6. perlscan: 2.01st. Clear:RC:1(10.0.0.185):. Processed in 0.884793 secs); 15 Feb 2013 18:28:15 -0000 Received: from unknown (HELO ucimail4.uci.cu) (10.0.0.185) by 0 with SMTP; 15 Feb 2013 18:28:14 -0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by ucimail4.uci.cu (Postfix) with ESMTP id 28E8E14C4022; Fri, 15 Feb 2013 13:28:14 -0500 (EST) X-Virus-Scanned: amavisd-new at uci.cu Received: from ucimail4.uci.cu ([127.0.0.1]) by localhost (ucimail4.uci.cu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wXMbGclNmjLx; Fri, 15 Feb 2013 13:28:13 -0500 (EST) Received: from ucimail4.uci.cu (ucimail4.uci.cu [10.0.0.185]) by ucimail4.uci.cu (Postfix) with ESMTP id 07A7314C4019; Fri, 15 Feb 2013 13:28:13 -0500 (EST) Date: Fri, 15 Feb 2013 13:28:12 -0500 (EST) From: " Marcos Ortiz Valmaseda" To: abhishek Cc: Michael Segel , common-user@hadoop.apache.org Subject: Re: How to handle sensitive data Message-ID: <8b2102a3-e6e0-4ee2-a29f-eb7a6fa926d1@ucimail4.uci.cu> In-Reply-To: Content-Type: multipart/alternative; boundary="=_f3e3d366-5983-43f4-a705-fb2090536248" MIME-Version: 1.0 X-Mailer: Zimbra 7.1.3_GA_3346 (ZimbraWebClient - FF3.0 (Win)/7.1.3_GA_3346) X-Virus-Checked: Checked by ClamAV on apache.org --=_f3e3d366-5983-43f4-a705-fb2090536248 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Regards, abhishek. I=C2=B4m agree with Michael. You can encrypt your incoming data from your a= pplication. I recommend to use HBase too. ----- Mensaje original ----- De: "Michael Segel" Para: common-user@hadoop.apache.org CC: cdh-user@cloudera.org Enviados: Viernes, 15 de Febrero 2013 8:47:16 Asunto: Re: How to handle sensitive data Simple, have your app encrypt the field prior to writing to HDFS. Also consider HBase. On Feb 14, 2013, at 10:35 AM, abhishek wrote: > >> Hi all, >> >> we are having some sensitive data, in some particular fields(columns). C= an I know how to handle sensitive in Hadoop. >> >> How do different people handle sensitive data in Hadoop. >> >> Thanks >> Abhi > Michael Segel | (m) 312.755.9623 Segel and Associates -- Marcos Ortiz Valmaseda, Product Manager && Data Scientist at UCI Blog : http://marcosluis2186.posterous.com LinkedIn: http://www.linkedin.com/in/marcosluis2186 Twitter : @marcosluis2186 --=_f3e3d366-5983-43f4-a705-fb2090536248--