[Bug]: Using dataX to import files into native MySQL there are redundant \n character

[ysjemmm]

ODC version

ODC432

OB version

independent

What happened?

when the customer performs the import operation based on the original MySQL, it will find that the first field of the imported data has an extra \n character starting from the second row

What did you expect to happen?

no extra \n character in the first field

How can we reproduce it (as minimally and precisely as possible)?

You need to prepare a native MySQL database with any table. then prepare a csv file, create an import work order, and import data to the specified table

CREATE TABLE `asset_schedule_pcl_20240902_temp` (
  `ID` bigint NOT NULL AUTO_INCREMENT,
  `ASSET_CODE` varchar(32) DEFAULT NULL COMMENT '借据编号',
  `pay_date` date DEFAULT NULL,
  `PAY_AMT_TOTAL` decimal(18,4) DEFAULT NULL COMMENT '还款总额',
  PRIMARY KEY (`ID`),
  KEY `IDX_ASSET_CODE` (`ASSET_CODE`)
) ENGINE=InnoDB AUTO_INCREMENT=4601617 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_0900_ai_ci

csv file: 1111.csv

Anything else we need to know?

No response