Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ SELECT * FROM orders$lake$snapshots;

When you specify the `$lake` suffix in a query, the table behaves like a standard Paimon table and inherits all its capabilities.
This allows you to take full advantage of Flink's query support and optimizations on Paimon, such as querying system tables, time travel, and more.
For further information, refer to Paimons [SQL Query documentation](https://paimon.apache.org/docs/1.3/flink/sql-query/#sql-query).
For further information, refer to Paimon's [SQL Query documentation](https://paimon.apache.org/docs/1.3/flink/sql-query/#sql-query).

#### Union Read of Data in Fluss and Paimon

Expand Down Expand Up @@ -176,6 +176,7 @@ The following table shows the mapping between [Fluss data types](table-design/da
| BINARY | BINARY |
| BYTES | BYTES |
| ARRAY\<t\> | ARRAY\<t\> |
| MAP\<kt, vt\> | MAP\<kt, vt\> |
| ROW\<n0 t0, n1 t1, ...\><br/>ROW\<n0 t0 'd0', n1 t1 'd1', ...\> | ROW\<n0 t0, n1 t1, ...\><br/>ROW\<n0 t0 'd0', n1 t1 'd1', ...\> |

## Snapshot Metadata
Expand Down
1 change: 1 addition & 0 deletions website/docs/table-design/data-types.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,5 +29,6 @@ Fluss has a rich set of native data types available to users. All the data types
| BINARY(n) | A fixed-length binary string (=a sequence of bytes) where n is the number of bytes. n must have a value between 1 and Integer.MAX_VALUE (both inclusive). |
| BYTES | A variable-length binary string (=a sequence of bytes). |
| ARRAY\<t\> | An array of elements with same subtype. <br/>Compared to the SQL standard, the maximum cardinality of an array cannot be specified but is fixed at 2,147,483,647. Also, any valid type is supported as a subtype.<br/>The type can be declared using ARRAY\<t\> where t is the data type of the contained elements. |
| MAP\<kt, vt\> | An associative array that maps keys to values. A map cannot contain duplicate keys; each key can map to at most one value. Map keys are always non-nullable and will be automatically converted to non-nullable types if a nullable key type is provided. There is no restriction of key types; it is the responsibility of the user to ensure uniqueness. The map type is an extension to the SQL standard.<br/>The type can be declared using MAP\<kt, vt\> where kt is the data type of the key elements and vt is the data type of the value elements. |
| ROW\<n0 t0, n1 t1, ...\><br/>ROW\<n0 t0 'd0', n1 t1 'd1', ...\> | A sequence of fields. <br/>A field consists of a field name, field type, and an optional description. The most specific type of a row of a table is a row type. In this case, each column of the row corresponds to the field of the row type that has the same ordinal position as the column. <br/>Compared to the SQL standard, an optional field description simplifies the handling with complex structures. <br/>A row type is similar to the STRUCT type known from other non-standard-compliant frameworks. <br/>The type can be declared using ROW\<n0 t0 'd0', n1 t1 'd1', ...\> where n is the unique name of a field, t is the logical type of a field, d is the description of a field. |