laglangyue opened a new issue, #4334:
URL: https://github.com/apache/incubator-seatunnel/issues/4334

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   
![image](https://user-images.githubusercontent.com/35491928/224524296-c889ea58-3ce3-4063-a0fe-19a8daf807d6.png)
   dataframe row
   
![image](https://user-images.githubusercontent.com/35491928/224524303-b4041a9a-fb4d-426c-b50e-452a0ca9838a.png)
   internal Row 
   
   
![image](https://user-images.githubusercontent.com/35491928/224524328-348b991a-fd38-4c0b-a0b1-55adcd7d8243.png)
   
   
   as the code above,
   `dataframe row  -> internal row -> st-row -> transform map->   transform 
output st-row -> internal row -> date type convert -> dataframe row `
   
   
   actually,dataframe row (DataSet<Row>) is different form internalRow,the 
trait con't convert,internalRow Binary storage row,dataframeRow is a row base 
on the scala dataType like st-row
   we can implement the convert line: `dataframe row -> st-row -> transform 
map->  transform output st-row -> dataframe row` 
   
   ### SeaTunnel Version
   
   dev
   
   ### SeaTunnel Config
   
   ```conf
   nothing
   ```
   
   
   ### Running Command
   
   ```shell
   nothing,in example
   ```
   
   
   ### Error Exception
   
   ```log
   convert array and map will exception
   ```
   
   
   ### Flink or Spark Version
   
   _No response_
   
   ### Java or Scala Version
   
   _No response_
   
   ### Screenshots
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] 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