MaxCompute:FROM_CHARSET

Syntax

STRING FROM_CHARSET(binary <source>, string <source_charset>[, string <mode>])

Parameters

source

Required. Type: BINARY. The binary data to decode.

source_charset

Required. Type: STRING. The source encoding of the binary data. Valid values: UTF-8, UTF-16, UTF-16LE, UTF-16BE, ISO-8859-1, US-ASCII, GB2312, GBK, GB18030.

mode

Optional. Type: STRING. The behavior when a character cannot be converted. If not specified, the function reports an error and stops execution. Valid values:

Return value

Returns a STRING value in UTF-8 encoding.

Examples

Example 1: Decode UTF-8 encoded binary data with TRANSLIT mode

SELECT FROM_CHARSET(unhex('e58aa0e6b2b9e9949fe696a4e68bb70a'), 'UTF-8', 'TRANSLIT');

Result:

+------------+
| _c0        |
+------------+
| 加油锟斤拷
     |
+------------+

Example 2: Decode GBK-encoded binary data

SELECT FROM_CHARSET(unhex('b9feb9febac3a4ce'), 'GBK');

Result:

+------------+
| _c0        |
+------------+
| 哈哈好の       |
+------------+

Example 3: Null input returns null

SELECT FROM_CHARSET(unhex('b9feb9febac3a4ce'), null);

Result:

+------------+
| _c0        |
+------------+
| NULL       |
+------------+

What's next

• MaxCompute supports user-defined functions (UDFs) when built-in functions do not meet your requirements. See UDF overview.

• For MaxCompute SQL FAQ and common errors, see:

  • FAQ about DDL operations

  • FAQ about DML operations

  • FAQ about DQL operations

  • Other SQL FAQ

  • Common errors for built-in functions

  • FAQ about built-in functions