-
Notifications
You must be signed in to change notification settings - Fork 13.9k
[FLINK-30868][table-api] Fix to use origin LongSerializer for seriali… #21827
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
Conversation
lincoln-lil
left a comment
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.
@fsk119 It's greate we can reserve the compatibility for 1.17 by this patch! Only some comments for the testing.
flink-table/flink-table-common/src/main/java/org/apache/flink/table/utils/TableSchemaUtils.java
Show resolved
Hide resolved
| @SuppressWarnings("unchecked") | ||
| public TypeSerializer<Timestamp> createSerializer(ExecutionConfig executionConfig) { | ||
| return (TypeSerializer) LocalDateTimeSerializer.INSTANCE; | ||
| return (TypeSerializer) LongSerializer.INSTANCE; |
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.
Any tests releated to this change?
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.
They modify the TimeIndicatorTypeInfo is because it will break the test FunctionITCase#testAggregateFunction. Now I revert the change in the TimeIndicatorTypeInfo and make sure the test still passes. So I think the origin test is enough.
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.
ok
lincoln-lil
left a comment
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.
LGTM
| @SuppressWarnings("unchecked") | ||
| public TypeSerializer<Timestamp> createSerializer(ExecutionConfig executionConfig) { | ||
| return (TypeSerializer) LocalDateTimeSerializer.INSTANCE; | ||
| return (TypeSerializer) LongSerializer.INSTANCE; |
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.
ok
…zation in the TimeIndicatorTypeInfo
…zation in the TimeIndicatorTypeInfo (apache#21827)
…zation in the TimeIndicatorTypeInfo (apache#21827)
…zation in the TimeIndicatorTypeInfo (apache#21827) (cherry picked from commit 48a2e5a)
…zation in the TimeIndicatorTypeInfo
What is the purpose of the change
Revert the API change in the #21182 to use the origin LongSerializer.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (yes / no)Documentation