| commit | c7363689ac85fb05a705c2d2eacd085569e4802c | [log] [tgz] |
|---|---|---|
| author | Wendy Wang <wendy.wang10@sap.com> | Thu May 02 17:24:43 2024 +0200 |
| committer | Wendy Wen Wang <wendy.wang10@sap.com> | Mon May 06 10:46:24 2024 +0000 |
| tree | 9e1acee11c10dfd128ac5a02ddd0b95c5d52740a | |
| parent | d7572a0784b371925b94e0024b980f0f28ba3cc0 [diff] |
Include time zone in event timestamp for Spanner implementation Google Cloud Spanner adds seven hours to java.sql.Timestamp objects when converting to UTC, resulting in entries being timestamped as occurring in the future. I believe this is related to their treatment of Timestamp literals, which assume a default time zone of America/Los_Angeles: https://cloud.google.com/spanner/docs/reference/standard-sql/lexical#timestamp_literals Using Instant includes the time zone in the String which keeps the timestamp accurate in Spanner. Change-Id: I313af4fbd7803478fb0604913ee2d781de37c895