Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

...

If the REFRESH_MODE is specified at the time of table creation, its priority is higher than freshness, which means freshness will no longer be used to infer the refresh mode of the dynamic table.

Full Refresh Mode

In full refresh mode, for dynamic table, the default overwrite behavior is table granularity. If a dynamic table is a partitioned table, and the time partition field format is specified by 'partition.fields.#.date-formatter' when creating the table, the default overwrite behavior is partition granularity, that is, only the latest partition data is overwritten each time. For more details on 'partition.fields.#.date-formatter', see the partitioned table full refresh section.

Operations on dynamic tables are executed through the following Alter statements.

...

1. Dynamic Table is a new conceptual entity and table type that also includes attributes such as query, freshness and refresh job, which makes it more appropriate to use the new interface.
2. If CatalogTable adds a new attribute that is not supported by Dynamic Table, it will lead to a conflict, so it is more appropriate to represent it using an interface that is parallel to CatalogTable.

Compatibility, Deprecation, and Migration Plan

This is new feature which doesn't change current behaviors.

Test Plan

...

1. .

...

Reference

[1] https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/concepts/dynamic_tables

...