terrymanu commented on issue #35533:
URL:
https://github.com/apache/shardingsphere/issues/35533#issuecomment-3642990049
## Problem Understanding
- During incremental migration, only changed columns are updated. When the
target table has ON UPDATE CURRENT_TIMESTAMP, the target auto-updates the time
even if that column wasn’t in the SET clause, causing a mismatch with the
source.
## Root Cause
- Pipeline is designed to update only columns marked as changed; the
target table’s ON UPDATE is its own behavior and still fires when the column is
omitted, leading to time drift.
## Analysis
- This is a usage/schema interaction, not a core-line bug. Recommended
practice is to avoid target-side auto-update side effects during migration or
raise timestamp precision so the column is treated as changed. A built-in
“update all columns/UPSERT all columns” mode
increases write amplification and conflict risk and isn’t a current
priority.
## Conclusion
- Pipeline isn’t a mainline focus; no change planned. If the current
behavior is unacceptable, please work around it (e.g., temporarily remove ON
UPDATE or increase column precision).
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
