[
https://issues.apache.org/jira/browse/FLINK-38308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-38308:
-----------------------------------
Labels: pull-request-available (was: )
> Prevent excessive logging from parsing SQL timestamps/dates
> -----------------------------------------------------------
>
> Key: FLINK-38308
> URL: https://issues.apache.org/jira/browse/FLINK-38308
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Runtime
> Affects Versions: 2.0.0
> Reporter: Roman Khachatryan
> Assignee: Roman Khachatryan
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2
>
>
> When using SQL functions like `TO_TIMESTAMP`, parse exceptions are logged at
> INFO level for invalid inputs, causing two issues:
> # Logging potentially sensitive data
> # Overloading logging system
>
> The behavior of returning NULL seems to be consistent with other functions
> (although not clearly documented in
> [https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/functions/systemfunctions/#temporal-functions)|https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/functions/systemfunctions/#temporal-functions]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
