[
https://issues.apache.org/jira/browse/FLINK-37753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser updated FLINK-37753:
-----------------------------------
Description:
Right now, running a UNIX_TIMESTAMP like:
{code:sql}
SELECT UNIX_TIMESTAMP('2025-04-30T19:20:17Z');
{code}
Returns a value like
{noformat}
-9223372036854776000
{noformat}
Instead of returning the minimum of a LONG, we could return an error because
the format is not according to the provider (in this case, the default) format
was:
Right now, running a UNIX_TIMESTAMP like:
{code:sql}
SELECT UNIX_TIMESTAMP('2025-04-30T19:20:17Z');
{code}
Returns a value like `-9223372036854776000`
Instead of returning the minimum of a LONG, we could return an error because
the format is not according to the provider (in this case, the default) format
> Improve error handling for UNIX_TIMESTAMP
> -----------------------------------------
>
> Key: FLINK-37753
> URL: https://issues.apache.org/jira/browse/FLINK-37753
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API
> Reporter: Martijn Visser
> Priority: Major
>
> Right now, running a UNIX_TIMESTAMP like:
> {code:sql}
> SELECT UNIX_TIMESTAMP('2025-04-30T19:20:17Z');
> {code}
> Returns a value like
> {noformat}
> -9223372036854776000
> {noformat}
> Instead of returning the minimum of a LONG, we could return an error because
> the format is not according to the provider (in this case, the default) format
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
