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

   ### 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
   
   从mysql同步数据到starrocks,seaTunnel在starrocks中自动建的表字段没有注释
   
   ### SeaTunnel Version
   
   2.3.8
   
   ### SeaTunnel Config
   
   ```conf
   env {
     parallelism = 2
     job.mode = "BATCH"
   }
   source {
       Jdbc {
           url = "jdbc:mysql://127.0.0.1:3306/test"
           driver = "com.mysql.jdbc.Driver"
           connection_check_timeout_sec = 100
           user = ""
           password = ""
           table_path = "test.student"
           query = "select  * from test.student"
       }
   }
   
   sink {
     StarRocks {
       nodeUrls = ["127.0.0.1:8030"]
       base-url = "jdbc:mysql://127.0.0.1:9030/"
       username = 
       password = 
       database = "test"
       table = "student"
       batch_max_rows = 10000
       enable_upsert_delete = true
       data_save_mode = DROP_DATA
       starrocks.config = {
         format = "JSON"
         strip_outer_array = true
       }
     }
   }
   ```
   
   
   ### Running Command
   
   ```shell
   ./bin/seatunnel.sh --config ./job/mysql-to-starrocks.conf -m local
   ```
   
   
   ### Error Exception
   
   ```log
   自动在starrocks中建的表没有注释
   ```
   
   
   ### Zeta or Flink or Spark Version
   
   2.3.8
   
   ### Java or Scala Version
   
   java 8
   
   ### 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