This is an automated email from the ASF dual-hosted git repository.

lzljs3620320 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/paimon.git


The following commit(s) were added to refs/heads/master by this push:
     new c3a83195f [doc] fix flink procedure document sql syntax error. (#4504)
c3a83195f is described below

commit c3a83195f40ea33f07a447d4d39f98890e4a4334
Author: Kerwin <[email protected]>
AuthorDate: Tue Nov 12 22:24:19 2024 +0800

    [doc] fix flink procedure document sql syntax error. (#4504)
---
 docs/content/flink/procedures.md             | 2 +-
 docs/content/maintenance/manage-snapshots.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/content/flink/procedures.md b/docs/content/flink/procedures.md
index d55a8dadd..7e669a89d 100644
--- a/docs/content/flink/procedures.md
+++ b/docs/content/flink/procedures.md
@@ -409,7 +409,7 @@ All available procedures are listed below.
       <td>expire_snapshots</td>
       <td>
          -- Use named argument<br/>
-         CALL [catalog.]sys.reset_consumer(<br/>
+         CALL [catalog.]sys.expire_snapshots(<br/>
             `table` => 'identifier', <br/>
             retain_max => 'retain_max', <br/>
             retain_min => 'retain_min', <br/>
diff --git a/docs/content/maintenance/manage-snapshots.md 
b/docs/content/maintenance/manage-snapshots.md
index eed0f72c0..721d5d0ba 100644
--- a/docs/content/maintenance/manage-snapshots.md
+++ b/docs/content/maintenance/manage-snapshots.md
@@ -308,9 +308,9 @@ submit a `remove_orphan_files` job to clean them:
 
 {{< tab "Spark SQL/Flink SQL" >}}
 ```sql
-CALL sys.remove_orphan_files(`table` => "my_db.my_table", [older_than => 
"2023-10-31 12:00:00"])
+CALL sys.remove_orphan_files(`table` => 'my_db.my_table', [older_than => 
'2023-10-31 12:00:00'])
 
-CALL sys.remove_orphan_files(`table` => "my_db.*", [older_than => "2023-10-31 
12:00:00"])
+CALL sys.remove_orphan_files(`table` => 'my_db.*', [older_than => '2023-10-31 
12:00:00'])
 ```
 {{< /tab >}}
 

Reply via email to