[Bug]: Support INSERT ON DUPLICATE KEY UPDATE for cluster table

[DanielZhangQD]

Is there an existing issue for the same bug?

• I have checked the existing issues.

Environment

- Version or commit-id (e.g. v0.1.0 or 8b23a93): d9cef7845
- Hardware parameters:
- OS type:
- Others:

Actual Behavior

• Create a cluster table

CREATE CLUSTER TABLE `statement_cx` (
`statement_id` VARCHAR(36) NOT NULL,
`account` VARCHAR(300) NOT NULL,
`response_at` DATETIME DEFAULT NULL,
`cx` DECIMAL(23,3) NOT NULL,
`account_id` INT UNSIGNED NOT NULL COMMENT 'the account_id added by the mo',
PRIMARY KEY (`statement_id`,`account_id`)
)

• Insert record with the following SQL and error is reported:

Error 20105 (HY000): not supported: INSERT ... ON DUPLICATE KEY UPDATE ... for cluster table\nPrevious DML conflicts with existing constraints or data format. This transaction has to be aborted","elapsed":"1.003875ms","rows":0,"sql":"INSERT INTO `mo_catalog`.`statement_cx` (`statement_id`,`account`,`response_at`,`cx`,`account_id`) VALUES ('0fe8d454-514d-11ee-9262-1e00ea3e7482','3cd4dac5_6592_47c0_88a1_0628544bf024','2023-09-12 17:16:35','0.0001234069009675',1),('1adec454-514d-11ee-9262-1e00ea3e7482','3cd4dac5_6592_47c0_88a1_0628544bf024','2023-09-12 17:16:55','0.027634048460035',1) ON DUPLICATE KEY UPDATE `statement_id`=`statement_id`

Expected Behavior

SQL is executed successfully

Steps to Reproduce

See detail in `Actual Behavior`

Additional information

Related to #11224 (comment)

[ouyuanning]

明天看

[ouyuanning]

PR待合并

[DanielZhangQD]

To be verified

[DanielZhangQD]

Verified and passed with commit 16d885502

[DanielZhangQD]

@aressu1985 Please help verify this issue.