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 C58981068B for ; Fri, 12 Apr 2013 23:30:16 +0000 (UTC) Received: (qmail 95242 invoked by uid 500); 12 Apr 2013 23:30:16 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 94968 invoked by uid 500); 12 Apr 2013 23:30:16 -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 94959 invoked by uid 500); 12 Apr 2013 23:30:16 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 94956 invoked by uid 99); 12 Apr 2013 23:30:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Apr 2013 23:30:16 +0000 Date: Fri, 12 Apr 2013 23:30:16 +0000 (UTC) From: "Gunther Hagleitner (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-4320) Consider extending max limit for precision to 38 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630754#comment-13630754 ] Gunther Hagleitner commented on HIVE-4320: ------------------------------------------ Review: https://reviews.facebook.net/D10227 > Consider extending max limit for precision to 38 > ------------------------------------------------ > > Key: HIVE-4320 > URL: https://issues.apache.org/jira/browse/HIVE-4320 > Project: Hive > Issue Type: Bug > Reporter: Gunther Hagleitner > Assignee: Gunther Hagleitner > Attachments: HIVE-4320.1.patch > > > Max precision of 38 still fits in 128. It changes the way you do math on these numbers though. Need to see if there will be perf implications, but there's a strong case to support 38 (instead of 36) to comply with other DBs. (Oracle, SQL Server, Teradata). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira