• numeric

• numeric

Returns a string from string1 which extracted with a specified regular expression string2 and a regex match group index integer.

The regex match group index starts from 1 and 0 means matching the whole regex. In addition, the regex match group index should not exceed the number of the defined groups.

E.g. REGEXP_EXTRACT(‘foothebar’, ‘foo(.?)(bar)’, 2)” returns “bar”.

Returns the specified part from the URL. Valid values for string2 include ‘HOST’, ‘PATH’, ‘QUERY’, ‘REF’, ‘PROTOCOL’, ‘AUTHORITY’, ‘FILE’, and ‘USERINFO’. Returns NULL if any of arguments is NULL.

E.g., parse_url(‘http://facebook.com/path1/p.php?k1=v1&k2=v2#Ref1’, ‘HOST’), returns ‘facebook.com’.

Also a value of a particular key in QUERY can be extracted by providing the key as the third argument string3.

E.g., parse_url(‘http://facebook.com/path1/p.php?k1=v1&k2=v2#Ref1’, ‘QUERY’, ‘k1’) returns ‘v1’.

Parses an interval string in the form “dd hh:mm:ss.fff” for SQL intervals of milliseconds or “yyyy-mm” for SQL intervals of months. An interval range might be DAY, MINUTE, DAY TO HOUR, or DAY TO SECOND for intervals of milliseconds; YEAR or YEAR TO MONTH for intervals of months.

E.g., INTERVAL ‘10 00:00:00.004’ DAY TO SECOND, INTERVAL ‘10’ DAY, or INTERVAL ‘2-10’ YEAR TO MONTH return intervals.

Converts a date time string string1 with format string2 (by default: yyyy-MM-dd HH:mm:ss if not specified) to Unix timestamp (in seconds), using the specified timezone in table config.

If a time zone is specified in the date time string and parsed by UTC+X format such as “yyyy-MM-dd HH:mm:ss.SSS X”, this function will use the specified timezone in the date time string instead of the timezone in table config. If the date time string can not be parsed, the default value Long.MIN_VALUE(-9223372036854775808) will be returned.

Flink SQL> SET ‘table.local-time-zone’ = ‘Europe/Berlin’;
— Returns 25201
Flink SQL> SELECT UNIX_TIMESTAMP(‘1970-01-01 08:00:01.001’, ‘yyyy-MM-dd HH:mm:ss.SSS’);
— Returns 1
Flink SQL> SELECT UNIX_TIMESTAMP(‘1970-01-01 08:00:01.001 +0800’, ‘yyyy-MM-dd HH:mm:ss.SSS X’);
— Returns 25201
Flink SQL> SELECT UNIX_TIMESTAMP(‘1970-01-01 08:00:01.001 +0800’, ‘yyyy-MM-dd HH:mm:ss.SSS’);
— Returns -9223372036854775808
Flink SQL> SELECT UNIX_TIMESTAMP(‘1970-01-01 08:00:01.001’, ‘yyyy-MM-dd HH:mm:ss.SSS X’);

Returns the current watermark for the given rowtime attribute, or NULL if no common watermark of all upstream operations is available at the current operation in the pipeline. The return type of the function is inferred to match that of the provided rowtime attribute, but with an adjusted precision of 3. For example, if the rowtime attribute is TIMESTAMP_LTZ(9), the function will return TIMESTAMP_LTZ(3).

Note that this function can return NULL, and you may have to consider this case. For example, if you want to filter out late data you can use:

WHERE
  CURRENT_WATERMARK(ts) IS NULL
  OR ts > CURRENT_WATERMARK(ts)

Returns the first argument that is not NULL.

If all arguments are NULL, it returns NULL as well. The return type is the least restrictive, common type of all of its arguments. The return type is nullable if all arguments are nullable as well.

— Returns ‘default’
COALESCE(NULL, ‘default’)
— Returns the first non-null value among f0 and f1,
— or ‘default’ if f0 and f1 are both NULL
COALESCE(f0, f1, ‘default’)

Returns null_replacement if input is NULL; otherwise input is returned.

Compared to COALESCE or CASE WHEN, this function returns a data type that is very specific in terms of nullability. The returned type is the common type of both arguments but only nullable if the null_replacement is nullable.

The function allows to pass nullable columns into a function or table that is declared with a NOT NULL constraint.

E.g., IFNULL(nullable_column, 5) returns never NULL.

Determine whether a given string is valid JSON.

Specifying the optional type argument puts a constraint on which type of JSON object is allowed. If the string is valid JSON, but not that type, false is returned. The default is VALUE.

— TRUE
‘1’ IS JSON
‘[]’ IS JSON
‘{}’ IS JSON
— TRUE
‘“abc”‘ IS JSON
— FALSE
‘abc’ IS JSON
NULL IS JSON
— TRUE
‘1’ IS JSON SCALAR
— FALSE
‘1’ IS JSON ARRAY
— FALSE
‘1’ IS JSON OBJECT
— FALSE
‘{}’ IS JSON SCALAR
— FALSE
‘{}’ IS JSON ARRAY
— TRUE
‘{}’ IS JSON OBJECT

Determines whether a JSON string satisfies a given path search criterion.

If the error behavior is omitted, FALSE ON ERROR is assumed as the default.

— TRUE
SELECT JSON_EXISTS(‘{“a”: true}’, ‘$.a’);
— FALSE
SELECT JSON_EXISTS(‘{“a”: true}’, ‘$.b’);
— TRUE
SELECT JSON_EXISTS(‘{“a”: [{ “b”: 1 }]}’,
  ‘$.a[0].b’);
— TRUE
SELECT JSON_EXISTS(‘{“a”: true}’,
  ‘strict $.b’ TRUE ON ERROR);
— FALSE
SELECT JSON_EXISTS(‘{“a”: true}’,
  ‘strict $.b’ FALSE ON ERROR);

Serializes a value into JSON.

This function returns a JSON string containing the serialized value. If the value is NULL, the function returns NULL.

— NULL
JSON_STRING(CAST(NULL AS INT))
— ‘1’
JSON_STRING(1)
— ‘true’
JSON_STRING(TRUE)
— ‘“Hello, World!”‘
JSON_STRING(‘Hello, World!’)
— ‘[1,2]’
JSON_STRING(ARRAY[1, 2])

Extracts a scalar from a JSON string.

This method searches a JSON string for a given path expression and returns the value if the value at that path is scalar. Non-scalar values cannot be returned. By default, the value is returned as STRING. Using dataType a different type can be chosen, with the following types being supported:

• VARCHAR / STRING
• BOOLEAN
• INTEGER
• DOUBLE

For empty path expressions or errors a behavior can be defined to either return null, raise an error or return a defined default value instead. When omitted, the default is NULL ON EMPTY or NULL ON ERROR, respectively. The default value may be a literal or an expression. If the default value itself raises an error, it falls through to the error behavior for ON EMPTY, and raises an error for ON ERROR.

For path contains special characters such as spaces, you can use [‘property’] or [“property”] to select the specified property in a parent object. Be sure to put single or double quotes around the property name. When using JSON_VALUE in SQL, the path is a character parameter which is already single quoted, so you have to escape the single quotes around property name, such as JSON_VALUE(‘{“a b”: “true”}’, ‘$.[‘’a b’’]’).

— “true”
JSON_VALUE(‘{“a”: true}’, ‘$.a’)
— TRUE
JSON_VALUE(‘{“a”: true}’, ‘$.a’ RETURNING BOOLEAN)
— “false”
JSON_VALUE(‘{“a”: true}’, ‘lax $.b’
    DEFAULT FALSE ON EMPTY)
— “false”
JSON_VALUE(‘{“a”: true}’, ‘strict $.b’
    DEFAULT FALSE ON ERROR)
— 0.998D
JSON_VALUE(‘{“a.b”: [0.998,0.996]}’,’$.[“a.b”][0]’ 
    RETURNING DOUBLE)
— “right”
JSON_VALUE(‘{“contains blank”: “right”}’, ‘strict $.[‘’contains blank’’]’ NULL ON EMPTY DEFAULT ‘wrong’ ON ERROR)

Extracts JSON values from a JSON string.

The result is returned as a STRING or ARRAY<STRING>. This can be controlled with the RETURNING clause.

The wrappingBehavior determines whether the extracted value should be wrapped into an array, and whether to do so unconditionally or only if the value itself isn’t an array already.

onEmpty and onError determine the behavior in case the path expression is empty, or in case an error was raised, respectively. By default, in both cases null is returned. Other choices are to use an empty array, an empty object, or to raise an error.

— ‘{ “b”: 1 }’
JSON_QUERY(‘{ “a”: { “b”: 1 } }’, ‘$.a’)
— ‘[1, 2]’
JSON_QUERY(‘[1, 2]’, ‘$’)
— NULL
JSON_QUERY(CAST(NULL AS STRING), ‘$’)
— ‘[“c1”,”c2”]’
JSON_QUERY(‘{“a”:[{“c”:”c1”},{“c”:”c2”}]}’,
    ‘lax $.a[].c’)
— [‘c1’,’c2’]
JSON_QUERY(‘{“a”:[{“c”:”c1”},{“c”:”c2”}]}’, ‘lax $.a[].c’ RETURNING ARRAY<STRING>)
— Wrap result into an array
— ‘[{}]’
JSON_QUERY(‘{}’, ‘$’ WITH CONDITIONAL ARRAY WRAPPER)
— ‘[1, 2]’
JSON_QUERY(‘[1, 2]’, ‘$’ WITH CONDITIONAL ARRAY WRAPPER)
— ‘[[1, 2]]’
JSON_QUERY(‘[1, 2]’, ‘$’ WITH UNCONDITIONAL ARRAY WRAPPER)
— Scalars must be wrapped to be returned
— NULL
JSON_QUERY(1, ‘$’)
— ‘[1]’
JSON_QUERY(1, ‘$’ WITH CONDITIONAL ARRAY WRAPPER)
— Behavior if path expression is empty / there is an error
— ‘{}’
JSON_QUERY(‘{}’, ‘lax $.invalid’ EMPTY OBJECT ON EMPTY)
— ‘[]’
JSON_QUERY(‘{}’, ‘strict $.invalid’ EMPTY ARRAY ON ERROR)

Builds a JSON object string from a list of key-value pairs.

Note that keys must be non-NULL string literals, while values may be arbitrary expressions.

This function returns a JSON string. The ON NULL behavior defines how to treat NULL values. If omitted, NULL ON NULL is assumed by default.

Values which are created from another JSON construction function call (JSON_OBJECT, JSON_ARRAY) are inserted directly rather than as a string. This allows building nested JSON structures.

— ‘{}’
JSON_OBJECT()
— ‘{“K1”:”V1”,”K2”:”V2”}’
JSON_OBJECT(‘K1’ VALUE ‘V1’, ‘K2’ VALUE ‘V2’)
— Expressions as values
JSON_OBJECT(‘orderNo’ VALUE orders.orderId)
— ON NULL
JSON_OBJECT(KEY ‘K1’ VALUE CAST(NULL AS STRING) NULL ON NULL)   — ‘{“K1”:null}’
JSON_OBJECT(KEY ‘K1’ VALUE CAST(NULL AS STRING) ABSENT ON NULL) — ‘{}’
— ‘{“K1”:{“K2”:”V”}}’
JSON_OBJECT(
  KEY ‘K1’
  VALUE JSON_OBJECT(
    KEY ‘K2’
    VALUE ‘V’
  )
)

Builds a JSON array string from a list of values.

This function returns a JSON string. The values can be arbitrary expressions. The ON NULL behavior defines how to treat NULL values. If omitted, ABSENT ON NULL is assumed by default.

Elements which are created from another JSON construction function call (JSON_OBJECT, JSON_ARRAY) are inserted directly rather than as a string. This allows building nested JSON structures.

— ‘[]’
JSON_ARRAY()
— ‘[1,”2”]’
JSON_ARRAY(1, ‘2’)
— Expressions as values
JSON_ARRAY(orders.orderId)
— ON NULL
JSON_ARRAY(CAST(NULL AS STRING) NULL ON NULL) — ‘[null]’
JSON_ARRAY(CAST(NULL AS STRING) ABSENT ON NULL) — ‘[]’
— ‘[[1]]’
JSON_ARRAY(JSON_ARRAY(1))

implicit constructor with parenthesis

(value1 [, value2])

explicit ROW constructor with

ROW(value1 [, value2])

Returns a row created from a list of values (value1, value2,…).

The implicit row constructor requires at least two fields. The explicit row constructor can deal with an arbitrary number of fields. Both of them support arbitrary expressions as fields.

Builds a JSON object string by aggregating key-value expressions into a single JSON object.

The key expression must return a non-nullable character string. Value expressions can be arbitrary, including other JSON functions. If a value is NULL, the ON NULL behavior defines what to do. If omitted, NULL ON NULL is assumed by default.

Note that keys must be unique. If a key occurs multiple times, an error will be thrown.

This function is currently not supported in OVER windows.

— ‘{“Apple”:2,”Banana”:17,”Orange”:0}’
SELECT
  JSON_OBJECTAGG(KEY product VALUE cnt)
FROM orders

Builds a JSON object string by aggregating items into an array.

Item expressions can be arbitrary, including other JSON functions. If a value is NULL, the ON NULL behavior defines what to do. If omitted, ABSENT ON NULL is assumed by default.

This function is currently not supported in OVER windows, unbounded session windows, or hop windows.

— ‘[“Apple”,”Banana”,”Orange”]’
SELECT
  JSON_ARRAYAGG(product)
FROM orders