search

ddavisqa / google-refine

Automatically exported from code.google.com/p/google-refine
0 stars 0 forks source link

Load into freebase: date objects are not converted into proper freebase dates #226

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Load some dataset containing dates
2. Convert dates from any text format using toDate() function
3. Now dates are displayed in grid like 2009-01-21T00:00:00Z
4. Align columns to freebase schema so column with dates will be property with 
type /type/datetime
5. Load data into freebase sandbox
6. refinery.freebaseapps.com says:

LOAD_TRIPLE triple is not valid to be loaded    (ERROR): Invalid literal Wed Jan 
21 00:00:00 MSK 2009 of type /type/datetime: Literal value (Wed Jan 21 00:00:00 
MSK 2009) must be valid mql datetime    
"$Name_en_0" --(/internet/website/launched)--> "Wed Jan 21 00:00:00 MSK 2009" 
[{"recon":{"s":"rec1289912419390812104"}}]

What is the expected output? What do you see instead?
Expecting that date type should be converted into freebase date format 
transparently.

What version of the product are you using? On what operating system?
2.0-r1836
Windows XP i386 32-bit
Oracle Java 6 update 22 (build 1.6.0_22-b04)

Please provide any additional information below.
Maybe related to issue 90 (toString() format parameter is ignored):
http://code.google.com/p/google-refine/issues/detail?id=90

Original issue reported on code.google.com by incredible.angst on 16 Nov 2010 at 10:50

GoogleCodeExporter commented 8 years ago 
Presumably this is meant to reference issue 184

Original comment by tfmorris on 26 Nov 2010 at 11:06

GoogleCodeExporter commented 8 years ago

Original comment by stefa...@google.com on 24 Dec 2010 at 8:08

GoogleCodeExporter commented 8 years ago 
This is still broken in 2.5 (and SVN).  I need it to work, so I'll take a look.

Original comment by tfmorris on 3 Mar 2012 at 7:20

GoogleCodeExporter commented 8 years ago 
Apologies for the long delay in getting this fixed.  It's repaired in r2451.

If you want to workaround the issue before the next release is available, you 
should be able to get things to work by converting the date to an ISO 8601 
string yourself before attempting the load into Freebase. 

    value.toString("yyyy-MM-dd'T'HH:mm:ss'Z'")

Original comment by tfmorris on 3 Mar 2012 at 9:42

GoogleCodeExporter commented 8 years ago

Original comment by tfmorris on 18 Sep 2012 at 3:05