Skip to content

Conversation

@fsk119
Copy link
Member

@fsk119 fsk119 commented Feb 2, 2023

…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:

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

Documentation

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

@flinkbot
Copy link
Collaborator

flinkbot commented Feb 2, 2023

CI report:

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

Copy link
Contributor

@lincoln-lil lincoln-lil left a 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.

@SuppressWarnings("unchecked")
public TypeSerializer<Timestamp> createSerializer(ExecutionConfig executionConfig) {
return (TypeSerializer) LocalDateTimeSerializer.INSTANCE;
return (TypeSerializer) LongSerializer.INSTANCE;
Copy link
Contributor

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?

Copy link
Member Author

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

Copy link
Contributor

@lincoln-lil lincoln-lil left a 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;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@fsk119 fsk119 merged commit 48a2e5a into apache:master Feb 6, 2023
akkinenivijay pushed a commit to krisnaru/flink that referenced this pull request Feb 11, 2023
mohsenrezaeithe pushed a commit to mohsenrezaeithe/flink that referenced this pull request Feb 21, 2023
@fsk119 fsk119 deleted the fix-comment branch March 8, 2023 01:24
Tan-JiaLiang pushed a commit to Tan-JiaLiang/flink that referenced this pull request Mar 4, 2024
…zation in the TimeIndicatorTypeInfo (apache#21827)

(cherry picked from commit 48a2e5a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants