Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-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 1135CD9EB for ; Tue, 14 Aug 2012 23:21:14 +0000 (UTC) Received: (qmail 2624 invoked by uid 500); 14 Aug 2012 23:21:12 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 2562 invoked by uid 500); 14 Aug 2012 23:21:12 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 2551 invoked by uid 99); 14 Aug 2012 23:21:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 23:21:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of edlinuxguru@gmail.com designates 209.85.160.176 as permitted sender) Received: from [209.85.160.176] (HELO mail-gh0-f176.google.com) (209.85.160.176) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Aug 2012 23:21:05 +0000 Received: by ghbz10 with SMTP id z10so1405541ghb.35 for ; Tue, 14 Aug 2012 16:20:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=/yXet+ODcatdmGegX1FQ971TtTKQ4+s5bgrvQnXM9EM=; b=Gl8MOvFiSRZW4abIRJ6zsPJe3dSq3SdaptuECWM53kjCk9Z49Y2vbA8871xf3YLlAu nosmncNfzUiOlO3TckapQIKspaJjaI44fEigBz5egOjlOfeAajFtEfz3fIHkrRECS2RA 6DST7qwdi1dX59xPcADH0+mYHrmpb9/3ytk3mLMwxp3Ta2E74aGbU+zOOx4ei233l0y9 arlXbLSS8lU0+OR/9ru7ZJV1rrMMEKytiFm5PgdwKX4zw5rOKkIYxoOFQOvySzOXnkG/ +Tz4764uDnnvChzl6U8l59JxHRFAvzzt148OY5pa0ZPTL53vhISQGGyo5TrztJeOIsPQ XCpg== MIME-Version: 1.0 Received: by 10.50.135.70 with SMTP id pq6mr11456416igb.29.1344986444289; Tue, 14 Aug 2012 16:20:44 -0700 (PDT) Received: by 10.64.86.227 with HTTP; Tue, 14 Aug 2012 16:20:44 -0700 (PDT) In-Reply-To: References: <7073291669E5764EB68B5914AC4204744E2EC3C2AB@AUSP01VMBX11.collaborationhost.net> Date: Tue, 14 Aug 2012 19:20:44 -0400 Message-ID: Subject: Re: Upper case column names From: Edward Capriolo To: "user@hive.apache.org" Content-Type: multipart/alternative; boundary=e89a8f64306a3d55ab04c7420f20 --e89a8f64306a3d55ab04c7420f20 Content-Type: text/plain; charset=ISO-8859-1 Just changing the code is not as easy as it sounds. It sounds like this will break many things in production for a lot of people. On Tuesday, August 14, 2012, Travis Crawford wrote: > Hey Mayank - > I've looked briefly at case-sensitivity in Hive, and there's a lot of places where fields are lowercased to normalize. For HCatalog, I'm playing around with a small patch that makes case-sensitivity optional and it works if you run queries with Pig/HCat against the metastore. It would be a pretty large patch to make hive optionally case sensitive though. > Case sensitive field names as an option certainly would use helpful though. > --travis > > On Tue, Aug 14, 2012 at 8:24 AM, Mayank Bansal wrote: >> >> Hi, >> >> >> >> The column names in hive are by default case insensitive. >> >> I was wondering if there is any way, I could make the column names case sensitive? >> >> I am running a model on a data, the data is now stored in hive, the model has columns referred in camel case. >> >> It would require a lot of effort to change the code of the model, so I was wondering if I could change my hive schema or anything. >> >> Would changing the metastore_db help in someway ? >> >> >> >> Thanks, >> >> Mayank >> >> >> >> ________________________________ >> This email message may contain proprietary, private and confidential information. The information transmitted is intended only for the person(s) or entities to which it is addressed. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may be illegal. If you received this in error, please contact the sender and delete the message from your system. >> >> Mu Sigma takes all reasonable steps to ensure that its electronic communications are free from viruses. However, given Internet accessibility, the Company cannot accept liability for any virus introduced by this e-mail or any attachment and you are advised to use up-to-date virus checking software. > > --e89a8f64306a3d55ab04c7420f20 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Just changing the code is not as easy as it sounds. It sounds like this= will break many things in production for a lot of people.
On Tuesday, A= ugust 14, 2012, Travis Crawford <traviscrawford@gmail.com> wrote:
> Hey Mayank -
> I've looked briefly at case-sensitivity in Hi= ve, and there's a lot of places where fields are lowercased to normaliz= e. For HCatalog, I'm playing around with a small patch that makes case-= sensitivity optional and it works if you run queries with Pig/HCat against = the metastore. It would be a pretty large patch to make hive optionally cas= e sensitive though.
> Case sensitive field names as an option certainly would use helpful th= ough.
> --travis
>
> On Tue, Aug 14, 2012 at 8:24 AM, May= ank Bansal <Mayank.Bansal@= mu-sigma.com> wrote:
>>
>> Hi,
>>
>> =A0
>>
>>= ; The column names in hive are by default case insensitive.
>>
= >> I was wondering if there is any way, I could make the column names= case sensitive?
>>
>> I am running a model on a data, the data is now stored= in hive, the model has columns referred in camel case.
>>
>= > It would require a lot of effort to change the code of the model, so I= was wondering if I could change my hive schema or anything.
>>
>> Would changing the metastore_db help in someway ?
&= gt;>
>> =A0
>>
>> Thanks,
>>
>= > Mayank
>>
>> =A0
>>
>> ___________= _____________________
>> This email message may contain proprietary, private and confidenti= al information. The information transmitted is intended only for the person= (s) or entities to which it is addressed. Any review, retransmission, disse= mination or other use of, or taking of any action in reliance upon, this in= formation by persons or entities other than the intended recipient is prohi= bited and may be illegal. If you received this in error, please contact the= sender and delete the message from your system.
>>
>> Mu Sigma takes all reasonable steps to ensure that its= electronic communications are free from viruses. However, given Internet a= ccessibility, the Company cannot accept liability for any virus introduced = by this e-mail or any attachment and you are advised to use up-to-date viru= s checking software.
>
> --e89a8f64306a3d55ab04c7420f20--