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

   ### Search before asking
   
   - [X] I had searched in the 
[feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22)
 and found no similar feature requirement.
   
   
   ### Description
   
   zh: 2.3.1版本的Kafka-source,似乎在解析复杂字段上不支持,比如如下的数据,没有办法解析到正确的字段。
   en: The Seatunnel  of version 2.3.1  kafka source  connnector  does not seem 
to support parsing complex fields, for example, it cannot parse the following 
data into the correct fields.
   
   ```json
   {
       "data": {
           "id": "data id",
           "create_time": "2023-06-06 20:00:12"
       }
   }
   ```
   
   ### Usage Scenario
   
   conf
   ```shell
   env {
     execution.parallelism = 1
     job.mode = "STREAMING"
   }
   
   source {
       kafka {
       result_table_name = "t1"
       consumer.group = "seatunnel_group"
       schema = {
         fields {
          data = {
             id = string
             create_time = string
          }
       }
       }
       format = json
       field_delimiter = ","
       topic = "topic_name"
       bootstrap.servers = "xxxxxxx"
       start_mode=timestamp
       start_mode.timestamp=1686587892000
     }
   }
   
   
   sink {
    Console {
     source_table_name="t1"
    }
   }
   ``` 
   out log
   <img width="1423" alt="image" 
src="https://github.com/apache/seatunnel/assets/23315594/c78e4b8f-86c2-4ef2-b917-2cf990cf99c4";>
   
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a 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