Return-Path: X-Original-To: apmail-avro-user-archive@www.apache.org Delivered-To: apmail-avro-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 3A21417AB7 for ; Fri, 23 Jan 2015 02:42:23 +0000 (UTC) Received: (qmail 2686 invoked by uid 500); 23 Jan 2015 02:42:23 -0000 Delivered-To: apmail-avro-user-archive@avro.apache.org Received: (qmail 2605 invoked by uid 500); 23 Jan 2015 02:42:23 -0000 Mailing-List: contact user-help@avro.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@avro.apache.org Delivered-To: mailing list user@avro.apache.org Received: (qmail 2584 invoked by uid 99); 23 Jan 2015 02:42:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2015 02:42:23 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vikas.saxena.2006@gmail.com designates 209.85.215.54 as permitted sender) Received: from [209.85.215.54] (HELO mail-la0-f54.google.com) (209.85.215.54) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jan 2015 02:41:57 +0000 Received: by mail-la0-f54.google.com with SMTP id hv19so4996013lab.13; Thu, 22 Jan 2015 18:40:25 -0800 (PST) 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=mJe1QAJCCSRTkbQO2hVRCsvTUYs0l+83WMR3VMLQOpo=; b=gWQxR12ljzv6HNJhOa+Vccpbe1PtlRqrHTA2MDkwus5TRpBj+jM+nmCuPBUCYgK02y StDWJnc9UQLLldYvi7LljQAWEviH59TZmxiUi1tsAaXYJ5jUx9Ic7UFBUzlrpDzllXEG 8lvkA+qNTdzj2SKKq+iunwBMgLoDXC1nVW211gzJ1tYDHiv1c80rwlfNyBeRY2dejjs8 EnY0PmhLLbg1sXK+vi9R7DaQ0lVCeqntASQ0FWCwqH5AFvWXmSuXEuPNnSyx3g2LZDkA tE/2c6E1OWEDA+PNL63v6rlTDKcj9YkwnMQ3wFZOit8VVTfjspdKVjlx5o6+Q6Tw1JtR YyBg== MIME-Version: 1.0 X-Received: by 10.112.8.41 with SMTP id o9mr4910398lba.40.1421980825223; Thu, 22 Jan 2015 18:40:25 -0800 (PST) Received: by 10.25.20.144 with HTTP; Thu, 22 Jan 2015 18:40:25 -0800 (PST) In-Reply-To: References: Date: Fri, 23 Jan 2015 13:40:25 +1100 Message-ID: Subject: Re: Enums in avro From: Vikas Saxena To: dev@avro.apache.org, user@avro.apache.org Content-Type: multipart/alternative; boundary=001a1134cf28f7074d050d48b54d X-Virus-Checked: Checked by ClamAV on apache.org --001a1134cf28f7074d050d48b54d Content-Type: text/plain; charset=UTF-8 Hi all, Any response?? On Mon, Jan 19, 2015 at 8:31 AM, Vikas Saxena wrote: > Hi Team, > We are using avro in our project to serialize telecom data and load it > into hive table. All our native telecom data fields are easily convertible > into hive data types. > The problem I am facing is for some of the enum fields that we have don't > start with 0 but start with 1000. > How can I design my schema to accommodate such enums? > -- Thanks and regards, Vikas Saxena. --001a1134cf28f7074d050d48b54d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,
Any response??

On Mon, Jan 19, 2015 at 8:31 AM, Vikas Saxe= na <vikas.saxena.2006@gmail.com> wrote:

Hi Team,
We are using avro in our project to serialize telecom data and load it into= hive table. All our native telecom data fields are easily convertible into= hive data types.
The problem I am facing is for some of the enum fields that we have don'= ;t start with 0 but start with 1000.
How can I design my schema to accommodate such enums?




--
Thanks and regards,
Vikas Saxena.
--001a1134cf28f7074d050d48b54d--