Skip to content

Conversation

@snuyanzin
Copy link
Contributor

What is the purpose of the change

The problem appears for materialized tables with non persisted columns after physical columns
small repro is

CREATE MATERIALIZED TABLE mt (id INT, metadata1 METADATA INT VIRTUAL, metadata2 METADATA INT VIRTUAL) AS SELECT 1 id;
ALTER MATERIALIZED TABLE mt AS SELECT 1 AS id, 'name' AS name;

Brief change log

MaterializedTableUtis and tests

Verifying this change

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): ( no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): ( no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): ( no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: ( no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable )

@flinkbot
Copy link
Collaborator

flinkbot commented Feb 12, 2026

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

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