You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hive.apache.org by Suhail Doshi <di...@gmail.com> on 2009/03/22 23:47:29 UTC

timestamp as a field name bug?

I am not sure if this is a bug or just undocumented as a reserved keyword
(or I missed it) but in case people don't know, apparently you cannot call a
field "timestamp":

hive> CREATE EXTERNAL TABLE page_views(project_code STRING, page STRING,
referrer STRING, ip INT, timestamp INT) ROW FORMAT DELIMITED FIELDS
TERMINATED BY '\001' LINES TERMINATED BY '\012' STORED AS TEXTFILE LOCATION
'/user/hadoop/data/logging/page_views';
FAILED: Parse Error: line 2:7 mismatched input 'EXTERNAL' expecting
TEMPORARY in create function statement

Time taken: 0.131 seconds
hive> CREATE EXTERNAL TABLE page_views(project_code STRING, page STRING,
referrer STRING, ip INT, created INT) ROW FORMAT DELIMITED FIELDS TERMINATED
BY '\001' LINES TERMINATED BY '\012' STORED AS TEXTFILE LOCATION
'/user/hadoop/data/logging/page_views';
OK
Time taken: 0.063 seconds

Suhail

Re: timestamp as a field name bug?

Posted by Suhail Doshi <di...@gmail.com>.
Ah, didn't think to do that, thanks.

On Sun, Mar 22, 2009 at 4:02 PM, Zheng Shao <zs...@gmail.com> wrote:

> HI Suhail,
>
> Please use `timestamp` as field name instead. Use backquota to escape the
> field name when needed.
>
>
> Zheng
>
>
> On Sun, Mar 22, 2009 at 3:47 PM, Suhail Doshi <di...@gmail.com>wrote:
>
>> I am not sure if this is a bug or just undocumented as a reserved keyword
>> (or I missed it) but in case people don't know, apparently you cannot call a
>> field "timestamp":
>>
>> hive> CREATE EXTERNAL TABLE page_views(project_code STRING, page STRING,
>> referrer STRING, ip INT, timestamp INT) ROW FORMAT DELIMITED FIELDS
>> TERMINATED BY '\001' LINES TERMINATED BY '\012' STORED AS TEXTFILE LOCATION
>> '/user/hadoop/data/logging/page_views';
>> FAILED: Parse Error: line 2:7 mismatched input 'EXTERNAL' expecting
>> TEMPORARY in create function statement
>>
>> Time taken: 0.131 seconds
>> hive> CREATE EXTERNAL TABLE page_views(project_code STRING, page STRING,
>> referrer STRING, ip INT, created INT) ROW FORMAT DELIMITED FIELDS TERMINATED
>> BY '\001' LINES TERMINATED BY '\012' STORED AS TEXTFILE LOCATION
>> '/user/hadoop/data/logging/page_views';
>> OK
>> Time taken: 0.063 seconds
>>
>> Suhail
>
>
>
>
> --
> Yours,
> Zheng
>



-- 
http://mixpanel.com
Blog: http://blog.mixpanel.com

Re: timestamp as a field name bug?

Posted by Zheng Shao <zs...@gmail.com>.
HI Suhail,

Please use `timestamp` as field name instead. Use backquota to escape the
field name when needed.


Zheng

On Sun, Mar 22, 2009 at 3:47 PM, Suhail Doshi <di...@gmail.com>wrote:

> I am not sure if this is a bug or just undocumented as a reserved keyword
> (or I missed it) but in case people don't know, apparently you cannot call a
> field "timestamp":
>
> hive> CREATE EXTERNAL TABLE page_views(project_code STRING, page STRING,
> referrer STRING, ip INT, timestamp INT) ROW FORMAT DELIMITED FIELDS
> TERMINATED BY '\001' LINES TERMINATED BY '\012' STORED AS TEXTFILE LOCATION
> '/user/hadoop/data/logging/page_views';
> FAILED: Parse Error: line 2:7 mismatched input 'EXTERNAL' expecting
> TEMPORARY in create function statement
>
> Time taken: 0.131 seconds
> hive> CREATE EXTERNAL TABLE page_views(project_code STRING, page STRING,
> referrer STRING, ip INT, created INT) ROW FORMAT DELIMITED FIELDS TERMINATED
> BY '\001' LINES TERMINATED BY '\012' STORED AS TEXTFILE LOCATION
> '/user/hadoop/data/logging/page_views';
> OK
> Time taken: 0.063 seconds
>
> Suhail




-- 
Yours,
Zheng