Versions Compared

Old Version 96

changes.mady.by.user ron liu

Saved on

compared with

New Version 97

changes.mady.by.user ron liu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To ensure that Flink SQL is semantically consistent in Streaming mode and Batch mode, combining the current situation of Flink and the needs of our business, choosing LEVEL-1 as the default behavior for Flink streaming and batch mode. If the user requires LEVEL-2 atomicity,  this ability can be achieved by enabling an table.cor-atomicity.table-as-select.atomicity-enabled option. In general, batch mode usually requires LEVEL-2 atomicity. In a nutshell, Flink provides two level atomicity guarantee, LEVEL-2 as the default behavior.

...

TableConfigOptions

Add table.cor-table-as-select.atomicity.-enabled option  option to allow users to enable atomicity when using create table as select syntax.

@PublicEvolving
public class TableConfigOptions {
    @Documentation.TableOption(execMode = Documentation.ExecMode.BATCH_STREAMING)
    public static final ConfigOption<Boolean> TABLE_COR_TABLE_AS_SELECT_ATOMICITY_ENABLED =
            key("table.cor-table-as-select.atomicity.-enabled")
                    .booleanType()
                    .defaultValue(false)
                    .withDescription(
                            "Specifies if the create table as select operation is executed atomically. "
                                  + "By default, the operation is non-atomic. The target table is created in Client side, and it will not be dropped even though the job fails or is cancelled. "
                                  + "If set this option to true, the target table is created in JM side, it also will be dropped when the job fails or is cancelled.");
}

...