raminqaf commented on code in PR #29973:
URL: https://github.com/apache/flink/pull/29973#discussion_r4597364605


##########
docs/content.zh/docs/sql/materialized-table/table-api.md:
##########
@@ -49,6 +49,11 @@ current catalog and database. The freshness is optional and 
defaults to
 The refresh mode is derived from the freshness (see [Refresh Mode]({{< ref 
"docs/sql/materialized-table/overview" >}}#refresh-mode)).
 Full refresh mode needs a workflow scheduler and cannot be used from a plain 
`TableEnvironment`.
 
+`execute()` creates the materialized table, or redeploys it if it already 
exists (see
+[Redeploying](#redeploying)). To refuse an existing object at the path, for 
example on a first
+deployment, call `execute(CreateMode.failIfExists())` instead. It fails if a 
table or view,
+temporary or not, already exists at the path, and leaves that object unchanged.

Review Comment:
   Very wordy. What is the default behavior here? So redeploys if it exists and 
with a explicit failIfExists we fail, correct?



-- 
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]

Reply via email to