Skip to content

[test][flink] Allow tag action tests to initialize custom catalogs - #10921

Merged
JingsongLi merged 1 commit into
apache:masterfrom
XiaoHongbo-Hope:codex/allow-tag-action-test-catalog
Nov 1, 2026
Merged

JingsongLi merged 1 commit into
apache:masterfrom
XiaoHongbo-Hope:codex/allow-tag-action-test-catalog

Conversation

@XiaoHongbo-Hope

Copy link
Copy Markdown
Contributor

What changed

TagActionITCase initialized its read/write test environment directly with a filesystem warehouse. Catalog-specific subclasses could override action creation but could not run the inherited create/delete tag test against their own catalog, so they had to skip it.

Route initialization in the three tag action tests through a protected method. The default method still uses the filesystem warehouse; subclasses can initialize their catalog's read/write environment before the inherited test body runs.

Validation

  • mvn -o -B -ntp -pl paimon-flink/paimon-flink-common -Pflink1 -Pfast-build -DwildcardSuites=none -Dtest=TagActionITCase test (12 tests passed)
  • mvn -o -B -ntp -pl paimon-flink/paimon-flink-common spotless:check

@XiaoHongbo-Hope XiaoHongbo-Hope changed the title [flink] Allow tag action tests to initialize custom catalogs [test][flink] Allow tag action tests to initialize custom catalogs Nov 1, 2026
@JingsongLi

Copy link
Copy Markdown
Contributor

+1

@JingsongLi
JingsongLi merged commit c03fab6 into apache:master Nov 1, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants