Return-Path: X-Original-To: apmail-hive-issues-archive@minotaur.apache.org Delivered-To: apmail-hive-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4F786174E6 for ; Wed, 15 Apr 2015 13:40:00 +0000 (UTC) Received: (qmail 11380 invoked by uid 500); 15 Apr 2015 13:40:00 -0000 Delivered-To: apmail-hive-issues-archive@hive.apache.org Received: (qmail 11358 invoked by uid 500); 15 Apr 2015 13:40:00 -0000 Mailing-List: contact issues-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 issues@hive.apache.org Received: (qmail 11346 invoked by uid 99); 15 Apr 2015 13:40:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Apr 2015 13:40:00 +0000 Date: Wed, 15 Apr 2015 13:40:00 +0000 (UTC) From: "Aihua Xu (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-9917) After HIVE-3454 is done, make int to timestamp conversion configurable 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-9917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated HIVE-9917: --------------------------- Attachment: HIVE-9917.patch > After HIVE-3454 is done, make int to timestamp conversion configurable > ---------------------------------------------------------------------- > > Key: HIVE-9917 > URL: https://issues.apache.org/jira/browse/HIVE-9917 > Project: Hive > Issue Type: Improvement > Reporter: Aihua Xu > Assignee: Aihua Xu > Attachments: HIVE-9917.patch > > > After HIVE-3454 is fixed, we will have correct behavior of converting int to timestamp. While the customers are using such incorrect behavior for so long, better to make it configurable so that in one release, it will default to old/inconsistent way and the next release will default to new/consistent way. And then we will deprecate it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)