Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 17 Aug 2012 06:15:38 +1100 (NCT)
From: "Neha Tomar (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <775923292.20563.1345144538424.JavaMail.jiratomcat@arcas>
In-Reply-To: <1658995660.8049.1341488794511.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HIVE-3228) unable to load null values that
 represent a timestamp value
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HIVE-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436245#comment-13436245 ] 

Neha Tomar commented on HIVE-3228:
----------------------------------

I don't think this issue is fixed as I am still seeing it. Can anyone pleases update?
                
> unable to load null values that represent a timestamp value
> -----------------------------------------------------------
>
>                 Key: HIVE-3228
>                 URL: https://issues.apache.org/jira/browse/HIVE-3228
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 0.8.0
>            Reporter: N Campbell
>         Attachments: CERT.TTS.txt
>
>
> Attempting to load delimited data into a table with one or more timestamp columns will fail when null values are represented in the input set.
> load data local inpath '....CERT.TTS.txt'
> overwrite into table CERT.TTS_E;
> insert overwrite table CERT.TTS  select * from CERT.TTS_E;
> Error: Query returned non-zero code: 9, cause: FAILED: Execution Error, return code 2 from org.apache.hadoop.hive.ql.exec.MapRedTask
> SQLState:  08S01
> ErrorCode: 9
> create table if not exists CERT.TTS_E ( RNUM int , CTS timestamp)
> row format delimited
> fields terminated by '\t'
> stored as textfile;
> create table if not exists CERT.TTS ( RNUM int , CTS timestamp) 
> stored as sequencefile;
> 0	
> 1	1996-01-01 00:00:00.000000000
> 2	1996-01-01 12:00:00.000000000
> 3	1996-01-01 23:59:30.123000000
> 4	2000-01-01 00:00:00.000000000
> 5	2000-01-01 12:00:00.000000000
> 6	2000-01-01 23:59:30.123000000
> 7	2000-12-31 00:00:00.000000000
> 8	2000-12-31 12:00:00.000000000
> 9	2000-12-31 12:15:30.123000000

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira