Return-Path: Delivered-To: apmail-hadoop-hive-user-archive@minotaur.apache.org Received: (qmail 66410 invoked from network); 26 Jan 2009 23:31:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 26 Jan 2009 23:31:40 -0000 Received: (qmail 84045 invoked by uid 500); 26 Jan 2009 23:31:40 -0000 Delivered-To: apmail-hadoop-hive-user-archive@hadoop.apache.org Received: (qmail 84026 invoked by uid 500); 26 Jan 2009 23:31:40 -0000 Mailing-List: contact hive-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hive-user@hadoop.apache.org Delivered-To: mailing list hive-user@hadoop.apache.org Received: (qmail 84017 invoked by uid 99); 26 Jan 2009 23:31:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 15:31:40 -0800 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of athusoo@facebook.com does not designate 69.63.179.25 as permitted sender) Received: from [69.63.179.25] (HELO mailout-snc1.facebook.com) (69.63.179.25) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Jan 2009 23:31:32 +0000 Received: from mail.thefacebook.com (intlb01.snat.snc1.facebook.com [10.128.203.16] (may be forged)) by pp01.snc1.tfbnw.net (8.14.1/8.14.1) with ESMTP id n0QNVB6T025122 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Mon, 26 Jan 2009 15:31:11 -0800 Received: from SC-MBXC1.TheFacebook.com ([192.168.18.102]) by sc-hub01.TheFacebook.com ([192.168.18.104]) with mapi; Mon, 26 Jan 2009 15:31:10 -0800 From: Ashish Thusoo To: "hive-user@hadoop.apache.org" Date: Mon, 26 Jan 2009 15:31:01 -0800 Subject: RE: Migration Strategy Thread-Topic: Migration Strategy Thread-Index: AcmACraHJM3cvz1nS2KE2Y2cxWmcSwAAvC0g Message-ID: <68B7689C98024D43B4C2709456F0B520096536FB5A@SC-MBXC1.TheFacebook.com> References: <19a16e8d0901261505k22da8c8ay2392347561be809f@mail.gmail.com> In-Reply-To: <19a16e8d0901261505k22da8c8ay2392347561be809f@mail.gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_68B7689C98024D43B4C2709456F0B520096536FB5ASCMBXC1TheFac_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.7400:2.4.4,1.2.40,4.0.166 definitions=2009-01-26_10:2009-01-21,2009-01-26,2009-01-26 signatures=0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_68B7689C98024D43B4C2709456F0B520096536FB5ASCMBXC1TheFac_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable If you are adding a column at the end of the table, you should be ok with t= he old data staying in the state that it was provided it is created with Me= tadataTypedColumnSetSerDe (I am not sure what happens with DynamicSerDe). M= etadataTypedColumnSetSerdDe interprets missing columns at the end as nulls = in the old data. Note this only works when adding columns at the end withou= t changing names... Ashish ________________________________ From: Josh Ferguson [mailto:josh@besquared.net] Sent: Monday, January 26, 2009 3:06 PM To: hive-user@hadoop.apache.org Subject: Migration Strategy What's the current strategy for when you have a production system and you r= ealize you need to add another column to the table or do some other thing? = Seems like you'd have to make a new table, run a script to transform and lo= ad all your old data to the new table, and then remove the old table. Is th= is what is currently being done? Josh F. --_000_68B7689C98024D43B4C2709456F0B520096536FB5ASCMBXC1TheFac_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable
If you are adding a column at the end of the table= , you=20 should be ok with the old data staying in the state that it was provided it= is=20 created with MetadataTypedColumnSetSerDe (I am not sure what happens with=20 DynamicSerDe). MetadataTypedColumnSetSerdDe interprets missing columns at t= he=20 end as nulls in the old data. Note this only works when adding columns at t= he=20 end without changing names...
 
Ashish
 <= /DIV>

From: Josh Ferguson [mailto:josh@besqua= red.net]=20
Sent: Monday, January 26, 2009 3:06 PM
To:=20 hive-user@hadoop.apache.org
Subject: Migration=20 Strategy

What's the current strategy for when you have a production syste= m and=20 you realize you need to add another column to the table or do some other th= ing?=20 Seems like you'd have to make a new table, run a script to transform and lo= ad=20 all your old data to the new table, and then remove the old table. Is this = what=20 is currently being done?

Josh F.
--_000_68B7689C98024D43B4C2709456F0B520096536FB5ASCMBXC1TheFac_--