Invalid Timestamp Value in Source Fields
| Applies To | Pipelines where a timestamp field in the Source table contains invalid values |
| Error Message Text(s) | org.apache.kafka.connect.data.Timestamp out of range [min: 0001-01-01T00:00:00Z, max: 9999-12-31T23:59:59Z]. Sample values: Jan 03, 0001 00:00:00 UTC |
Error Summary
Hevo ingests data from timestamp fields in the Source tables in Unix epoch format. This error occurs when Hevo fails to load an Event because a timestamp field in the Event contains a value outside the supported Unix epoch time range.
Potential Cause
A timestamp field in the Event contains values earlier than January 01, 0001 00:00:00 UTC or later than December 31, 9999 23:59:59 UTC.
Suggested Action(s)
-
Use Python Code-based Transformations to modify the timestamp values so that they are within the supported Unix epoch time range. For example, replace the invalid timestamp values with a valid datetime.
Note: You can view samples of the failed Events through the Objects section of the Pipeline Detailed View. This helps you identify invalid timestamps and test your Transformations on these Events before deploying.
-
Change the data type of the timestamp field to a type such as STRING or VARCHAR so that Hevo can ingest data from such fields as text.
Note: Changing the data type to a text data type may result in increased query costs in the Destination.
After applying any of the suggested actions, replay the failed Events to ensure that they are loaded successfully. If the failed Events are not loaded, contact Hevo Support.