This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/amoro.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 69c0f99da Regenerated Amoro latest docs page based on
38ef38134d54a7381a351b4f17cba42a6c5356ac commit
69c0f99da is described below
commit 69c0f99da24e9bbb341ae37bf9979b05a010abee
Author: GitHub Actions <[email protected]>
AuthorDate: Tue May 19 08:26:57 2026 +0000
Regenerated Amoro latest docs page based on
38ef38134d54a7381a351b4f17cba42a6c5356ac commit
---
output/docs/latest/ams-config/index.html | 15 ---------------
output/docs/latest/deployment/index.html | 3 +++
output/docs/latest/search.json | 2 +-
output/docs/latest/using-tables/index.html | 2 +-
4 files changed, 5 insertions(+), 17 deletions(-)
diff --git a/output/docs/latest/ams-config/index.html
b/output/docs/latest/ams-config/index.html
index 8cc7401bb..b98cc7a45 100644
--- a/output/docs/latest/ams-config/index.html
+++ b/output/docs/latest/ams-config/index.html
@@ -734,21 +734,6 @@ table td:last-child, table th:last-child { width: 40%;
word-break: break-all; }
<td>1 min</td>
<td>TTL for catalog metadata.</td>
</tr>
- <tr>
- <td>data-expiration.enabled</td>
- <td>true</td>
- <td>Enable data expiration</td>
- </tr>
- <tr>
- <td>data-expiration.interval</td>
- <td>1 d</td>
- <td>Execute interval for data expiration</td>
- </tr>
- <tr>
- <td>data-expiration.thread-count</td>
- <td>10</td>
- <td>The number of threads used for data expiring</td>
- </tr>
<tr>
<td>database.auto-create-tables</td>
<td>true</td>
diff --git a/output/docs/latest/deployment/index.html
b/output/docs/latest/deployment/index.html
index bf81f4791..5e96ef9f9 100644
--- a/output/docs/latest/deployment/index.html
+++ b/output/docs/latest/deployment/index.html
@@ -893,6 +893,8 @@ They are configured in
<code>$AMORO_CONF_DIR/plugins/process-factories.yaml</cod
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">clean-orphan-files.interval</span>: <span
style="color:#e6db74">"1d"</span> <span style="color:#75715e">#
interval for cleaning orphan files</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">clean-dangling-delete-files.enabled</span>: <span
style="color:#e6db74">"true"</span> <span style="color:#75715e">#
enable dangling delete files cleaning</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">clean-dangling-delete-files.interval</span>: <span
style="color:#e6db74">"1d"</span> <span style="color:#75715e">#
interval for cleaning dangling delete files</span>
+</span></span><span style="display:flex;"><span> <span
style="color:#f92672">expire-data.enabled</span>: <span
style="color:#e6db74">"true"</span> <span
style="color:#75715e"># enable data expiration</span>
+</span></span><span style="display:flex;"><span> <span
style="color:#f92672">expire-data.interval</span>: <span
style="color:#e6db74">"1d"</span> <span
style="color:#75715e"># interval for data expiration</span>
</span></span></code></pre></div><div class="info">
Process-level properties control whether an action is registered.
Table-level properties (see <a href="../../user-guides/configurations/">Table
Configurations</a>) control whether a specific table executes the action.
</div>
@@ -914,6 +916,7 @@ They are configured in
<code>$AMORO_CONF_DIR/plugins/execute-engines.yaml</code>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">pool.snapshots-expiring.thread-count</span>: <span
style="color:#ae81ff">10</span> <span style="color:#75715e"># thread
pool for snapshot expiration</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">pool.orphan-files-cleaning.thread-count</span>: <span
style="color:#ae81ff">10</span> <span style="color:#75715e"># thread pool
for orphan file cleaning</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">pool.clean-dangling-delete-files.thread-count</span>:
<span style="color:#ae81ff">10</span> <span style="color:#75715e"># thread
pool for dangling delete files cleaning</span>
+</span></span><span style="display:flex;"><span> <span
style="color:#f92672">pool.expire-data.thread-count</span>: <span
style="color:#ae81ff">10</span> <span style="color:#75715e">#
thread pool for data expiration</span>
</span></span><span style="display:flex;"><span> <span
style="color:#f92672">process.status.ttl</span>: <span style="color:#ae81ff">4h
</span> <span style="color:#75715e"># TTL for process
status cache</span>
</span></span></code></pre></div><div class="info">
Custom pools use the pattern <code>pool.<name>.thread-count</code>.
Processes select pools via their <code>tag()</code> method, falling back to the
default pool if no match.
diff --git a/output/docs/latest/search.json b/output/docs/latest/search.json
index 0e2046246..d959e285d 100644
--- a/output/docs/latest/search.json
+++ b/output/docs/latest/search.json
@@ -1 +1 @@
-[{"categories":null,"content":"Amoro Docs This directory contains the
documentation content of Amoro.\nThe documentation is written in Markdown
format. The images referenced in the documentation are saved in the images
folder. Style Proper nouns should start with a capital letter, like
Hadoop、Hive、Iceberg、Amoro
","description":"","title":"","uri":"https://amoro.apache.org/docs/latest/readme/"},{"categories":null,"content":";
AMS Configuration Amoro Management Service Configuration The con [...]
\ No newline at end of file
+[{"categories":null,"content":"Amoro Docs This directory contains the
documentation content of Amoro.\nThe documentation is written in Markdown
format. The images referenced in the documentation are saved in the images
folder. Style Proper nouns should start with a capital letter, like
Hadoop、Hive、Iceberg、Amoro
","description":"","title":"","uri":"https://amoro.apache.org/docs/latest/readme/"},{"categories":null,"content":";
AMS Configuration Amoro Management Service Configuration The con [...]
\ No newline at end of file
diff --git a/output/docs/latest/using-tables/index.html
b/output/docs/latest/using-tables/index.html
index ba7dea082..a56749068 100644
--- a/output/docs/latest/using-tables/index.html
+++ b/output/docs/latest/using-tables/index.html
@@ -759,7 +759,7 @@ Conversely, you can re-enable it:</p>
</span></span><span style="display:flex;"><span> <span
style="color:#e6db74">'self-optimizing.enabled'</span> <span
style="color:#f92672">=</span> <span
style="color:#e6db74">'false'</span>);
</span></span></code></pre></div><h2 id="configure-data-expiration">Configure
data expiration</h2>
<p>Amoro can periodically clean data based on the table’s expiration
policy, which includes properties such as whether to enable expiration,
retention duration, expiration level, and the selection of the field for
expiration.
-it’s also necessary for AMS to have the data expiration thread enabled.
You can enable the ‘data-expiration’ property in the configuration
file</p>
+it’s also necessary for AMS to have the data expiration process enabled.
You can enable the ’expire-data’ property in the process-factories
plugin configuration file</p>
<h3 id="enable-or-disable-data-expiration">Enable or disable data
expiration</h3>
<p>By default, Amoro has data expiration disabled. If you want to enable data
expiration, please execute the following command.</p>
<div class="highlight"><pre tabindex="0"
style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code
class="language-sql" data-lang="sql"><span style="display:flex;"><span><span
style="color:#66d9ef">ALTER</span> <span style="color:#66d9ef">TABLE</span>
test_db.test_log_store <span style="color:#66d9ef">set</span> tblproperties (
