Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ACA2D17B73 for ; Tue, 29 Sep 2015 00:38:58 +0000 (UTC) Received: (qmail 56069 invoked by uid 500); 29 Sep 2015 00:38:58 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 55990 invoked by uid 500); 29 Sep 2015 00:38:58 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 55977 invoked by uid 99); 29 Sep 2015 00:38:57 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Sep 2015 00:38:57 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 58CC91A2091 for ; Tue, 29 Sep 2015 00:38:57 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.901 X-Spam-Level: ** X-Spam-Status: No, score=2.901 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id hLeZz3Lv-DiL for ; Tue, 29 Sep 2015 00:38:51 +0000 (UTC) Received: from mail-yk0-f176.google.com (mail-yk0-f176.google.com [209.85.160.176]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 55EEE20314 for ; Tue, 29 Sep 2015 00:38:50 +0000 (UTC) Received: by ykdt18 with SMTP id t18so198849842ykd.3 for ; Mon, 28 Sep 2015 17:38:43 -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=WDoOPWUpxKwHGRpmxeVOrZ77LAFNJ7jvMZzUngFN1yU=; b=cJwaZ9BykyDlC/45gY9pOVXmRyr2nl7DekhIDFRe4DWKxT4kj++81MJmJ8CJCG04GW 18E0xrHjVrJt6rLZgdjLUmbUxkyOCPkou2w/+mad9y6OHZJhB/fRwSjw6AFzVQvUBZGm U0FXOWGggrPPXc8kcHu4pfCfYTh/zNYkCPXfJBmek/z9ww1GaeocGBvmxiSaTRpYhdbb R2n7uJoag0d4HP20jySxEWv4klN3g4ar+f4p/FBr43tCIi2ooO7BxxWt7Bm/MvjkWmod wQ1q2sHOHG+7lL3riFe2AWagupN8Mby6nqBj2+YwPWDx9IF6lHM9JWYj6nCMbA0aZgmq Q7rA== MIME-Version: 1.0 X-Received: by 10.129.119.84 with SMTP id s81mr17802209ywc.67.1443487123447; Mon, 28 Sep 2015 17:38:43 -0700 (PDT) Received: by 10.37.115.16 with HTTP; Mon, 28 Sep 2015 17:38:43 -0700 (PDT) In-Reply-To: References: Date: Mon, 28 Sep 2015 20:38:43 -0400 Message-ID: Subject: Re: Avro column type in Hive From: Chaoyu Tang To: dev@hive.apache.org Content-Type: multipart/alternative; boundary=001a1141c11a3b261d0520d80918 --001a1141c11a3b261d0520d80918 Content-Type: text/plain; charset=UTF-8 Yes, when you described the avro table, what you get back was actually from your avro schema instead of database table. The avro table is NOT considered as a metastore backed SerDe. But that it has its columns populated to DB (e.g. HIVE-6308 ) is mainly for column statistics purpose, which obviously is not applicable to your case which has a type name > 100kb. Chaoyu On Mon, Sep 28, 2015 at 8:12 PM, Sergey Shelukhin wrote: > Hi. > I noticed that when I create an Avro table using a very large schema file, > mysql metastore silently truncates the TYPE_NAME in COLUMNS_V2 table to > the size of varchar (4000); however, when I do describe on the table, it > still displays the whole type name (around 100Kb long) that I presume it > gets from deserializer. > Is the value in TYPE_NAME used for anything for Avro tables? > > --001a1141c11a3b261d0520d80918--