Bug Report: Using COPY to import Date type error.

[TKONIY]

I'm working importing SSB into heavydb. My source file date.tbl looks like.

19920101,"January 1, 1992","Thursday","January",1992,199201,"Jan1992",5,1,1,1,1,"Winter","0","1","1","1"
19920102,"January 2, 1992","Friday","January",1992,199201,"Jan1992",6,2,2,1,1,"Winter","0","1","0","1"
19920103,"January 3, 1992","Saturday","January",1992,199201,"Jan1992",7,3,3,1,1,"Winter","1","1","0","0"
19920104,"January 4, 1992","Sunday","January",1992,199201,"Jan1992",1,4,4,1,1,"Winter","0","1","0","0"
19920105,"January 5, 1992","Monday","January",1992,199201,"Jan1992",2,5,5,1,1,"Winter","0","1","0","1"
19920106,"January 6, 1992","Tuesday","January",1992,199201,"Jan1992",3,6,6,1,1,"Winter","0","1","0","1"
19920107,"January 7, 1992","Wednesday","January",1992,199201,"Jan1992",4,7,7,1,2,"Winter","0","1","0","1"
19920108,"January 8, 1992","Thursday","January",1992,199201,"Jan1992",5,8,8,1,2,"Winter","0","1","0","1"
19920109,"January 9, 1992","Friday","January",1992,199201,"Jan1992",6,9,9,1,2,"Winter","0","1","0","1"
19920110,"January 10, 1992","Saturday","January",1992,199201,"Jan1992",7,10,10,1,2,"Winter","1","1","0","0"
19920111,"January 11, 1992","Sunday","January",1992,199201,"Jan1992",1,11,11,1,2,"Winter","0","1","0","0"
19920112,"January 12, 1992","Monday","January",1992,199201,"Jan1992",2,12,12,1,2,"Winter","0","1","0","1"
19920113,"January 13, 1992","Tuesday","January",1992,199201,"Jan1992",3,13,13,1,2,"Winter","0","1","0","1"
19920114,"January 14, 1992","Wednesday","January",1992,199201,"Jan1992",4,14,14,1,3,"Winter","0","1","0","1"
19920115,"January 15, 1992","Thursday","January",1992,199201,"Jan1992",5,15,15,1,3,"Winter","0","1","0","1"

After import by

COPY date_ from '/heavydb/data/import/ssb10/date.tbl';

I found that all d_datekey (the 1st column) are 1970-08-20. Here's part of the result from SELECT *, in which the d_datekey is not coherent with other attributes.

d_datekey|d_date|d_dayofweek|d_month|d_year|d_yearmonthnum|d_yearmonth|d_daynuminweek|d_daynuminmonth|d_daynuminyear|d_monthnuminyear|d_weeknuminyear|d_sellingseason|d_lastdayinweekfl|d_lastdayinmonthfl|d_holidayfl|d_weekdayfl
1970-08-20|Octorber 1, 1998|Friday|Octorber|1998|199810|Oct1998|6|1|274|10|40|Fall|0|1|0|1
1970-08-20|Octorber 2, 1998|Saturday|Octorber|1998|199810|Oct1998|7|2|275|10|40|Fall|1|1|0|0
1970-08-20|Octorber 3, 1998|Sunday|Octorber|1998|199810|Oct1998|1|3|276|10|40|Fall|0|1|0|0
1970-08-20|Octorber 4, 1998|Monday|Octorber|1998|199810|Oct1998|2|4|277|10|40|Fall|0|1|0|1
1970-08-20|Octorber 9, 1998|Saturday|Octorber|1998|199810|Oct1998|7|9|282|10|41|Fall|1|1|0|0
1970-08-20|Octorber 10, 1998|Sunday|Octorber|1998|199810|Oct1998|1|10|283|10|41|Fall|0|1|0|0
1970-08-20|Octorber 11, 1998|Monday|Octorber|1998|199810|Oct1998|2|11|284|10|41|Fall|0|1|0|1
1970-08-20|Octorber 12, 1998|Tuesday|Octorber|1998|199810|Oct1998|3|12|285|10|41|Fall|0|1|0|1
1970-08-20|Octorber 17, 1998|Sunday|Octorber|1998|199810|Oct1998|1|17|290|10|42|Fall|0|1|0|0
1970-08-20|Octorber 18, 1998|Monday|Octorber|1998|199810|Oct1998|2|18|291|10|42|Fall|0|1|0|1

[cdessanti]

Hi,

When I run that benchmark I used the field as.an integer and I hadn't any problem.

Also if you look at our docs a numeric value like that is interpreted as an epoch, because in the end it's a number and it shouldn't interpreted as a date