-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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.
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
[Improve][Transform] Remove Fallback during parsing Transform process #6644
Conversation
cc @Hisoka-X |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for @xiaochen-zhou
@@ -476,8 +453,10 @@ public static SeaTunnelDataType<?> getProducedType(Action action) { | |||
.getProducedCatalogTable() | |||
.getSeaTunnelRowType(); | |||
} catch (UnsupportedOperationException e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should not throw UnsupportedOperationException
after this change.
} catch (UnsupportedOperationException e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should not throw
UnsupportedOperationException
after this change.
done.
Purpose of this pull request
Currently all Transform initialization can be done through TransFormFactory, so we can remove fallback code and deprecated SeaTunnelPluginLifeCycle interface.
Does this PR introduce any user-facing change?
no
How was this patch tested?
exist tests.
Check list
New License Guide
release-note
.