[FLINK-24586] SQL functions should return STRING instead of VARCHAR(2000)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.15.1, 1.16.0
• Component/s: Table SQL / API
• Labels: pull-request-available stale-assigned

Release Note

Functions that returned VARCHAR(2000) in 1.14, return VARCHAR with maximum length now. In particular this includes:

JSON_VALUE
CHR
REVERSE
SPLIT_INDEX
REGEXP_EXTRACT
PARSE_URL
FROM_UNIXTIME
DECODE
DATE_FORMAT
CONVERT_TZ

• Assignee: Nicholas Jiang
• Reporter: Ingo Bürk
• Created: 19/Oct/21 07:24
• Updated: 15/Jun/22 12:35
• Resolved: 12/Apr/22 08:30

Description

There are some SQL functions which currently return VARCHAR(2000). With more strict CAST behavior from FLINK-24413, this could become an issue.

The following functions return VARCHAR(2000) and should be changed to return STRING instead:

• JSON_VALUE
• JSON_QUERY
• JSON_OBJECT
• JSON_ARRAY

There are also some more functions which should be evaluated:

• CHR
• REVERSE
• SPLIT_INDEX
• PARSE_URL
• FROM_UNIXTIME
• DECODE

Issue Links

• is related to: FLINK-24413 Casting to a CHAR() and VARCHAR() doesn't trim the string to the specified precision
• links to: GitHub Pull Request #17691
• links to: GitHub Pull Request #19014