XuQianJin-Stars opened a new pull request #8746: [hotfix][FLINK-11120][table]fix the bug of timestampadd handles time URL: https://github.com/apache/flink/pull/8746 ## What is the purpose of the change *Fix the casting problem for function TIMESTAMPADD in Table* ## Brief change log - *In judging `ScalarOperators` `generateTemporalPlusMinus` function to add the following the `date` conversion `timestamp` of logic, are as follows:* ```scala case (TIME_WITHOUT_TIME_ZONE, INTERVAL_DAY_TIME) => generateOperatorIfNotNull(ctx, new TimeType(), left, right) { (l, r) => s"($l $op ((int) ($r))) % ${MILLIS_PER_DAY}" } case (TIME_WITHOUT_TIME_ZONE, INTERVAL_YEAR_MONTH) => generateOperatorIfNotNull(ctx, new TimeType(), left, right) { (l, r) => s"$l" } ``` ## Verifying this change *(Please pick either of the following options)* This change is a trivial rework / code cleanup without any test coverage. *(or)* This change is already covered by existing tests, such as *(please describe tests)*. *(or)* This change added tests and can be verified as follows: *(example:)* - *`TIMESTAMPADD` with time; returns a time value.The interval is positive for `ScalarFunctionsTest`. - *`TIMESTAMPADD` with time; returns a time value .The interval is negative for `ScalarFunctionsTest`. ## 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, Yarn/Mesos, 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)
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
