Since the differences in the two systems are due to their implementation, I'd say you have the following options:   1. Use a differnet type, e.g., STRING. When concerting from STRING to TIMESTAMP you will encounter the same issues though. 2. Change your ingestion pipeline to enforce a timestamp range that is valid in both systems. This assumes that your a date with year 0000 would be considered "garbage" by your application. 3. Live with the fact that a NULL timestamp could mean it is out of range.   May I ask what exactly is causing the headache? The fact that both systems return different results or the fact that for your application the year 0000 is a meaningful date? ... View more