Skip to content

test: assert streaming table partitioning survives non-full-refresh alter#1528

Open
sd-db wants to merge 2 commits into
mainfrom
sd-db/coverage/partitioning
Open

test: assert streaming table partitioning survives non-full-refresh alter#1528
sd-db wants to merge 2 commits into
mainfrom
sd-db/coverage/partitioning

Conversation

@sd-db

@sd-db sd-db commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

Streaming-table config changes that don't touch partition_by take the alter path, which issues CREATE OR REFRESH STREAMING TABLE ... PARTITIONED BY (...) rather than a full replace. There was no functional assertion that the existing partitioning actually survives that path: check_state_alter_change_is_applied verifies the refresh schedule, comment, and tblproperties, but never re-reads partition_by.

This adds a server-observable assertion to TestStreamingTableChangesApply::test_change_is_applied_via_alter: after a metadata-only alter, it re-reads the relation config and asserts partition_by == ["id"].

Testing

  • TestStreamingTableChangesApply::test_change_is_applied_via_alter — passed
  • TestStreamingTableChangesApply::test_change_is_applied_via_replace (regression; shares the helper) — passed
  • pre-commit run (ruff / ruff format / mypy) — passed

…lter

A metadata-only change to a streaming table takes the alter path, which
issues CREATE OR REFRESH rather than a full replace. Assert the existing
partitioning is retained so a regression that dropped the PARTITIONED BY
clause would be caught.
@sd-db sd-db requested a review from jprakash-db as a code owner June 16, 2026 12:28
@github-actions

Copy link
Copy Markdown

Coverage report

This PR does not seem to contain any modification to coverable code.

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.

1 participant