Return-Path: X-Original-To: apmail-pig-dev-archive@www.apache.org Delivered-To: apmail-pig-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 C7546DA78 for ; Sun, 2 Sep 2012 23:09:07 +0000 (UTC) Received: (qmail 10936 invoked by uid 500); 2 Sep 2012 23:09:07 -0000 Delivered-To: apmail-pig-dev-archive@pig.apache.org Received: (qmail 10898 invoked by uid 500); 2 Sep 2012 23:09:07 -0000 Mailing-List: contact dev-help@pig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pig.apache.org Delivered-To: mailing list dev@pig.apache.org Received: (qmail 10890 invoked by uid 500); 2 Sep 2012 23:09:07 -0000 Delivered-To: apmail-hadoop-pig-dev@hadoop.apache.org Received: (qmail 10886 invoked by uid 99); 2 Sep 2012 23:09:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Sep 2012 23:09:07 +0000 Date: Mon, 3 Sep 2012 10:09:07 +1100 (NCT) From: "Jie Li (JIRA)" To: pig-dev@hadoop.apache.org Message-ID: <1844759164.29212.1346627347425.JavaMail.jiratomcat@arcas> Subject: [jira] [Created] (PIG-2902) Pig defaults numeric types to integer instead of double MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jie Li created PIG-2902: --------------------------- Summary: Pig defaults numeric types to integer instead of double Key: PIG-2902 URL: https://issues.apache.org/jira/browse/PIG-2902 Project: Pig Issue Type: Bug Reporter: Jie Li This was observed in PIG-2835, where Pig defaults the type used in SUM() as integer while it's actually double, thus parsing each number to integer would throw an exception. PIG-2835 replaced the expensive exception handling with a light weight sanity check, but do we really want to default the numeric types to integer? -- 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