ddl: Fix an issue where a query may throw an error during a remote read and the precision of a duration data type is changed (release-6.5)

[JaySon-Huang]

This is an manual fix of #8671 in release-6.5

What problem does this PR solve?

Issue Number: close #8601

Problem Summary:

What is changed and how it works?

see #8601 (comment). The different in release-7.1 and earlier branches is because the fsp change of time column type is ignored

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Fix an issue where a query may throw an error during a remote read and the precision of a duration data type is changed.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Lloyd-Pottiger, SeaRise

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Lloyd-Pottiger,SeaRise]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-03-04 08:55:19.738465737 +0000 UTC m=+70946.760712124: ☑️ agreed by Lloyd-Pottiger.
• 2024-03-04 08:57:27.974654955 +0000 UTC m=+71074.996901344: ☑️ agreed by SeaRise.

[JaySon-Huang]

/run-all-tests

[Lloyd-Pottiger]

/run-unit-test