-Re: Strange error in Hive - Insert INTO
Jérôme Verdier 2013-08-19, 07:19
Thanks for your replies.
"So all that said, i see that the columns in your create table statement
don't match the columns in your outermost select statement. In particular,
DT_JOUR is listed as the 6th column in your create table statement but it
appears to be the 2nd column in your select statement. So something looks
It was the problem, i resolve my problem by giving the fields in the right
order, like they are in the CREATE TABLE.
Now, everything looks OK.
2013/8/14 Sanjay Subramanian <[EMAIL PROTECTED]>
> Another reason I can think of is possibly some STRING column in your
> table has a "DELIMITER" character…Like once in production I had tab spaces
> in the string and my table was also defined using TAB as delimiter
> From: Stephen Sprague <[EMAIL PROTECTED]>
> Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Date: Wednesday, August 14, 2013 8:43 AM
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Subject: Re: Strange error in Hive - Insert INTO
> Hi Jerome,
> That's a grandiose sql statement you got there! :) I find that if you
> break up those nested queries into simple CTAS (Create Table AS) statements
> and create a cascading effect of referring to the table in the previous
> step it makes debugging *so* much easier. In other SQL dialects like DB2
> this is facilitated by the WITH keyword. Maybe the Hive gurus will
> implement that some day. But that's a topic for another day.
> So all that said, i see that the columns in your create table statement
> don't match the columns in your outermost select statement. In particular,
> DT_JOUR is listed as the 6th column in your create table statement but it
> appears to be the 2nd column in your select statement. So something looks
> fishy there.
> My guess is ultimately you're missing a comma somewhere in the select
> list so hive is eating an column as a column alias and all your data is
> skewed over by one column. This happens not so infrequently since it is
> valid sql.
> Long winded answer to a simple question. Apologies up front!
> On Wed, Aug 14, 2013 at 5:35 AM, Jérôme Verdier <
> [EMAIL PROTECTED]> wrote:
>> Hi everybody,
>> I faced a strange error in Hive today.
>> I have launch a hive script to make some calculations, joins, union,
>> etc... and then insert these results in over hive table.
>> Everything is working fine (.hql is working, full ok, data are
>> imported), but one field (CO_RGRP_PRODUITS) is very strange.
>> after the insert, CO_RGRP_PRODUITS is looking like a TIMESTAMP
>> (1970-01-01 01:00:00) instead of being a simple STRING.
>> I precise that source field are simple string like this : 0101380,
>> for example
>> What is going wrong here.
>> You can find my script below (create table and .hql insert/calculations)
>> Thanks for your help.
>> INSERT SCRIPT :
>> CREATE TABLE default.THM_CA_RGRP_PRODUITS_JOUR (
>> CO_SOCIETE BIGINT,
>> TYPE_ENTITE STRING,
>> CODE_ENTITE STRING,
>> TYPE_RGRP_PRODUITS STRING,
>> CO_RGRP_PRODUITS STRING,
>> DT_JOUR TIMESTAMP,
>> MT_CA_NET_TTC FLOAT,
>> MT_OBJ_CA_NET_TTC FLOAT,
>> NB_CLIENTS FLOAT,
>> MT_CA_NET_TTC_COMP FLOAT,
>> MT_OBJ_CA_NET_TTC_COMP FLOAT,
>> NB_CLIENTS_COMP FLOAT);
>> INSERT SCRIPT :
>> INSERT INTO TABLE THM_CA_RGRP_PRODUITS_JOUR
>> 1 as
>> CO_SOCIETE,-- A modifier => variable
>> '2013-01-02 00:00:00.0' as
>> DT_JOUR, -- A modifier => variable
>> 'MAG' as
>> m.co_magasin as
>> 'FAM' as
>> sourceunion.CO_RGRP_PRODUITS as