Skip to content

[FLINK-38030][table-planner] Fix cast exception for TableLineageDatasetImpl when the catalog is not a AbstractCatalog #26739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 3, 2025
Merged

[FLINK-38030][table-planner] Fix cast exception for TableLineageDatasetImpl when the catalog is not a AbstractCatalog #26739

merged 1 commit into from
Jul 3, 2025

Conversation

xuyangzhong
Copy link
Contributor

BP #26737 to release-2.1

@xuyangzhong
[FLINK-38030][table-planner] Fix cast exception for TableLineageDatas…
b9c2cce 
…etImpl when the catalog is not a AbstractCatalog (apache#26727)

(cherry picked from commit 5497b71)
@flinkbot
Copy link
Collaborator

flinkbot commented Jul 2, 2025 •
edited
Loading

CI report:

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

@github-actions github-actions bot added community-reviewed-LGTM Applied if there are 2 non-committer approves on a PR. (The submitter cannot approve their own PR.) and removed community-reviewed-LGTM Applied if there are 2 non-committer approves on a PR. (The submitter cannot approve their own PR.) labels Jul 2, 2025
@xuyangzhong xuyangzhong merged commit 745e2bd into apache:release-2.1 Jul 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@RocMarshal RocMarshal RocMarshal approved these changes

@loserwang1024 loserwang1024 loserwang1024 approved these changes

Assignees
No one assigned
Labels
community-reviewed-LGTM Applied if there are 2 non-committer approves on a PR. (The submitter cannot approve their own PR.)
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@xuyangzhong @flinkbot @RocMarshal @loserwang1024