Occurrence.occurrenceDate before linux time get messed up

11700
Reporter: mdoering
Assignee: omeyn
Type: Improvement
Summary: Occurrence.occurrenceDate before linux time get messed up
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2012-08-20 19:31:52.32
Updated: 2013-12-17 15:17:25.261
Resolved: 2012-09-05 11:44:17.595
        
Description: might be a java date serialization problem. See for example this occurrence with May 27, 1947:
http://data.gbif.org/occurrences/11727389
http://jawa.gbif.org:8080/occurrence-ws/occurrence/11727389
http://jawa.gbif.org:8080/occurrence/11727389]]>
    

Author: omeyn@gbif.org
Created: 2012-08-21 09:06:37.168
Updated: 2012-08-21 09:22:04.008
        
Sorry, I don't understand the bug - can you clarify please?

Nevermind - Lars explained the issue is occurrence date is before epoch, so storing as ms since epoch doesn't make sense.
    

Author: lfrancke@gbif.org
Comment: You could just store a negative value
Created: 2012-08-21 09:34:29.088
Updated: 2012-08-21 09:34:29.088

Author: omeyn@gbif.org
Comment: Done some digging and this is not a problem with the OccurrencePersistenceService.  So now I'll check what sqooping in from mysql produces (the source of the example record).
Created: 2012-08-31 13:43:27.542
Updated: 2012-08-31 13:43:27.542

Author: omeyn@gbif.org
Comment: Confirmed that this is a problem with sqooping from mysql.  Will investigate further when the next copy from mysql is due.
Created: 2012-09-04 15:50:10.269
Updated: 2012-09-04 15:50:10.269

Author: omeyn@gbif.org
Comment: Was a type mismatch in hive and udf table definitions. Fixed in occurrence-process and udf.
Created: 2012-09-05 11:44:17.62
Updated: 2012-09-05 11:44:17.62