yinrui97 opened a new issue, #8444:
URL: https://github.com/apache/seatunnel/issues/8444

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   **Issue1**
   
   When reading csv file, if one field contains line break \n and this field is 
encapsulated by double quotation. see below example
   
   ```
   field1, field2,   "field3_a xxxxx
   \n. field3_b yyy", field4 ...
   ```
   
   Seatunnel can not handle such case and just report exception when reading 
such line.   If a field is encapsulated by double quotation mark, seatunnel 
should ignore the line break for this field.
   
   **Issue2**
   
   If a field is encapsulated by double quotation mark in a line,  after 
seatunnel reading the line, it can recognize the double quotation mark, see 
below example, a line has 4 fields
   
   ```
   field1, field2, "field3 xxxxx, field3 yyyyy", field4
   ```
   
   But when seatunnel writes the line in the sink csv file, the the double 
quotation mark is missing, see below example, , this line has 5 fields, this is 
wrong
   ```
   field1, field2, field3 xxxxx, field3 yyyyy, field4
   ```
    
   
   ### SeaTunnel Version
   
   2.3.8
   
   ### SeaTunnel Config
   
   ```conf
   This is a common issue, nothing to do with Seatunnel Config.
   ```
   
   
   ### Running Command
   
   ```shell
   This is common issue, very easy to reproduce.
   ```
   
   
   ### Error Exception
   
   ```log
   Issue1 has error exception, but issue2 has no error exception.
   ```
   
   
   ### Zeta or Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to