Error Message When Exporting with Dumpling

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dumpling导出有报错信息

| username: TiDBer_eIQDQW2z

Initially, Dumpling was using version 7.0.0. After following the community’s suggestion to match the TiDB version, the issue still persists.

Current situation:

TiDB version 6.5.1
image

Dumpling version 6.5.1

Error log:

Table structure with the error:

CREATE TABLE `a_group` (
  `oldjf` int(11) DEFAULT NULL,
  `newjf` int(11) DEFAULT NULL,
  `oldsj` datetime DEFAULT NULL,
  `newsj` datetime DEFAULT NULL,
  `createtime` datetime DEFAULT NULL,
  `yh` varchar(255) COLLATE utf8mb4_general_ci DEFAULT NULL,
  `id` bigint(20) NOT NULL AUTO_INCREMENT,
  `txt` varchar(255) COLLATE utf8mb4_general_ci DEFAULT NULL,
  `gmt_create` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP,
  `gmt_modified` datetime NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`) /*T![clustered_index] CLUSTERED */,
  KEY `aa` (`oldjf`),
  KEY `idx_gmt_create` (`gmt_create`),
  KEY `idx_gmt_modified` (`gmt_modified`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci AUTO_INCREMENT=30479
| username: 胡杨树旁 | Original post link

What is the export command? Can you check the dumpling logs?

| username: xingzhenxiang | Original post link

It seems like there is an issue with the tool, someone has encountered this before.

| username: TiDBer_eIQDQW2z | Original post link

The complete log of dumpling is as follows, no obvious issues were found. By the way, the export was successful, but now every time an export is performed, an alert is generated on the TiDB side. I want to remove this alert.

| username: 胡杨树旁 | Original post link

Will executing this SQL in the database also result in an error?

| username: tidb菜鸟一只 | Original post link

It’s probably an issue with the tool. Your table shouldn’t have a _tidb_rowid column, but the tool is still trying to query this column. It should be an issue with version 6.5.1. Try switching to version 6.5.2.

| username: dba-kit | Original post link

His table uses a clustered index and does not have the hidden primary key column _tidb_rowid, so the error is normal. However, dumpling should attempt to use _tidb_rowid for sharding, and if it fails, it will directly traverse according to the primary key.

| username: zhanggame1 | Original post link

It might be a tool version issue.

| username: 爱学习的TiDBer | Original post link

I also suggest changing the tool version, it might solve the problem.