You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/engine-flink/ddl.md
+30-1Lines changed: 30 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -222,6 +222,36 @@ DROP TABLE my_table;
222
222
This will entirely remove all the data of the table in the Fluss cluster.
223
223
224
224
## Alter Table
225
+
226
+
### Add Columns
227
+
228
+
Fluss allows you to evolve a table's schema by adding new columns. This is a lightweight, metadata-only operation that offers the following benefits:
229
+
230
+
-**Zero Data Rewrite**: Adding a column does not require rewriting or migrating existing data files.
231
+
-**Instant Execution**: The operation completes in milli-seconds, regardless of the table size.
232
+
-**Availability**: The table remains online and fully accessible throughout schema evolution, with no disruption to active clients.
233
+
234
+
Currently, this feature has the following characteristics:
235
+
236
+
-**Position**: New columns are always appended to the end of the existing column list.
237
+
-**Nullability**: Only nullable columns can be added to an existing table to ensure compatibility with existing data.
238
+
-**Type Support**: You can add columns of any data type, including complex types such as `ROW`, `MAP`, and `ARRAY`.
239
+
-**Nested Fields**: Currently, adding fields within an existing nested `ROW` is not supported. Such operations are categorized as "updating column types" and will be supported in future versions.
240
+
241
+
You can add a single column or multiple columns using the `ALTER TABLE statement.
The SET statement allows users to configure one or more connector options including the [Storage Options](engine-flink/options.md#storage-options) for a specified table. If a particular option is already configured on the table, it will be overridden with the new value.
227
257
@@ -249,7 +279,6 @@ The following example illustrates reset the `table.datalake.enabled` option to i
Copy file name to clipboardExpand all lines: website/docs/maintenance/operations/upgrade-notes-0.9.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,15 @@ sidebar_position: 4
7
7
8
8
These upgrade notes discuss important aspects, such as configuration, behavior, or dependencies, that changed between Fluss 0.8 and Fluss 0.9. Please read these notes carefully if you are planning to upgrade your Fluss version to 0.9.
9
9
10
+
## Adding Columns
11
+
12
+
Fluss storage format was designed with schema evolution protocols from day one. Therefore, tables created in v0.8 or earlier can immediately benefit from the `ADD COLUMN` feature after upgrading to v0.9 without dropping and re-creating table.
13
+
However, old clients (pre-v0.9) do not recognize the new schema versioning protocol. If an old client attempts to read data from a table that has undergone schema evolution, it may encounter decoding errors or data inaccessibility.
14
+
Therefore, it is crucial to ensure that all Fluss servers and all clients interacting with the Fluss cluster are upgraded to v0.9 before performing any schema modifications.
15
+
16
+
:::warning
17
+
Attempting to add columns while older clients (v0.8 or below) are still actively reading from the table will lead to Schema Inconsistency and may crash your streaming pipelines.
0 commit comments