Tartarus0zm commented on code in PR #22995:
URL: https://github.com/apache/flink/pull/22995#discussion_r1265020895
##########
docs/layouts/shortcodes/generated/table_config_configuration.html:
##########
@@ -21,10 +21,10 @@
<td>The name of the default database in the initial catalog to be
created when instantiating TableEnvironment.</td>
</tr>
<tr>
- <td><h5>table.ctas.atomicity-enabled</h5><br> <span class="label
label-primary">Batch</span> <span class="label
label-primary">Streaming</span></td>
+ <td><h5>table.rtas-ctas.atomicity-enabled</h5><br> <span
class="label label-primary">Batch</span> <span class="label
label-primary">Streaming</span></td>
<td style="word-wrap: break-word;">false</td>
<td>Boolean</td>
- <td>Specifies if the CREATE TABLE AS SELECT statement is executed
atomically. By default, the statement is non-atomic. The target table is
created on the client side, and it will not be dropped even though the job
fails or is canceled. If set this option to true and the underlying
DynamicTableSink implements the SupportsStaging interface, the statement is
expected to be executed atomically, the behavior of which depends on the actual
DynamicTableSink.</td>
+ <td>Specifies if the CREATE TABLE/REPLACE TABLE/CREATE OR REPLACE
AS SELECT statement is executed atomically. By default, the statement is
non-atomic. The target table is created/replaced on the client side, and it
will not be rollback even though the job fails or is canceled. If set this
option to true and the underlying DynamicTableSink implements the
SupportsStaging interface, the statement is expected to be executed atomically,
the behavior of which depends on the actual DynamicTableSink.</td>
Review Comment:
As we discussed, using rolled back
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
