bug: panic when UNIX epoch time out of i64 range

[MrCroxx]

Describe the bug

In https://github.com/risingwavelabs/risingwave/blob/v1.7.1/src/connector/src/parser/unified/json.rs#L438-L449 , we convert the input into i64 and parse the timestamp with it. RW will panic if the given range is out of i64 range.

Error message/log

2024-04-02 14:54:13 thread 'rw-streaming' panicked at src/connector/src/parser/unified/json.rs:447:52:
2024-04-02 14:54:13 called `Option::unwrap()` on a `None` value

To Reproduce

{
	"before": null,
	"after": {
	    "id": 12,
        "example_timestamp_tz": 12852202631933722624
    },
	"source": {
		"table": "pathmetadata"
	},
	"op": "c",
	"ts_ms": 1707225270445
}

Expected behavior

The timestamp should be Saturday, 9 April 2377.

How did you deploy RisingWave?

No response

The version of RisingWave

No response

Additional context

No response

[tabVersion]

I don't quite get the problem here, for a real-world workload, the json format limits integers by 2^53, much smaller than i64 range. The problem seems unreachable.

[xiangjinwu]

WIll not panic but will return err (and converted into null) after #16265

[github-actions]

This issue has been open for 60 days with no activity.
If you think it is still relevant today, and needs to be done in the near future, you can comment to update the status, or just manually remove the no-issue-activity label.
You can also confidently close this issue as not planned to keep our backlog clean. Don't worry if you think the issue is still valuable to continue in the future. It's searchable and can be reopened when it's time. 😄

[xxchan]

WIll not panic but will return err (and converted into null) after #16265

So this issue can be closed?