Skip to content

[AMORO-4512][Paimon] Support snapshot expiration - #4513

Open
csurong wants to merge 2 commits into
apache:masterfrom
csurong:feat/paimon-snapshot-expiration
Open

csurong wants to merge 2 commits into
apache:masterfrom
csurong:feat/paimon-snapshot-expiration

Conversation

@csurong

@csurong csurong commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Why are the changes needed?

Paimon tables with write-only=true need separate snapshot maintenance. AMS currently cannot schedule snapshot expiration for these tables.

This PR adds periodic Paimon snapshot expiration through the existing Process framework and shows task results in the Cleanup tab. Retention policies continue to come from the Paimon table.

This PR covers snapshot expiration only. Other Paimon maintenance actions can build on the same Process integration in follow-up changes.

Close #4512.

Brief change log

  • Add a Paimon ProcessFactory and snapshot expiration process using Paimon's native API, refreshing table settings and preserving catalog credentials during cleanup.
  • Add plugin configuration, a table-level switch and a dedicated execution pool. The plugin is disabled by default.
  • Reuse the shared Cleanup query and process lifecycle. Enable manual cancellation only for Paimon snapshot expiration, cover submission and retry races, and preserve cleanup on table removal. Keep Iceberg cancellation, partial commits and plugin-provided history unchanged.
  • Add user documentation, regression tests, Java 11/17 AMS integration coverage and a Paimon 1.1.1 CI job for the existing Scala 2.13 profile.

How was this patch tested?

  • Add some test cases that check the changes thoroughly including negative and positive cases if possible

  • Add screenshots for manual tests if appropriate

  • Run test locally before making a pull request

The latest fixes passed 58 focused tests on Java 11, including shared process lifecycle, cancellation races, and Iceberg cancellation and partial-commit regressions. The dashboard build and six Cleanup component tests also passed.

End-to-end verification on the latest code used Java 17, a local AMS and six real Paimon 1.2.0 tables. It covered automatic discovery, periodic expiration, configuration changes, cancellation from the dashboard and restart recovery. Current data and historical changelog reads remained intact with independent changelog retention.

Documentation

  • Does this pull request introduce a new feature? yes
  • If yes, how is the feature documented? docs — docs/formats/paimon.md

@github-actions github-actions Bot added type:docs Improvements or additions to documentation module:ams-server Ams server module type:infra type:build module:ams-dashboard Ams dashboard module module:common labels Nov 17, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

module:ams-dashboard Ams dashboard module module:ams-server Ams server module module:common type:build type:docs Improvements or additions to documentation type:infra

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Support periodic Paimon snapshot expiration in AMS

1 participant