zheng594 opened a new issue, #8013: URL: https://github.com/apache/seatunnel/issues/8013
### 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 { "password": "********", "driver": "com.mysql.cj.jdbc.Driver", "query": "select id as `id`,area_code as `area_code`,area_name as `area_name` from `test`.`lwx_test04`", "where_condition": "where create_time >'2024-11-11 11:00:00'", "fetch_size": 10000, "compatible_mode": "doris", "plugin_name": "Jdbc", "user": "user", "url": "url" } 上述配置报：ErrorCode:[JDBC-04], ErrorDescription:[Connector database failed] - open() failed.errCode = 2, detailMessage = Unknown column 'create_time' in 'table list' at…… 实际上create_time字段是存在的。 将 ： "query": "select id as `id`,area_code as `area_code`,area_name as `area_name` from `test`.`lwx_test04`", "where_condition": "where create_time >'2024-11-11 11:00:00'", 合并改成： "query": "select id as `id`,area_code as `area_code`,area_name as `area_name` from `test`.`lwx_test04` where create_time >'2024-11-11 11:00:00", sql能正常执行。 后续原因是create_time字段在query所在select字段中不存在所以报错，这个应该是一个bug ### SeaTunnel Version V2.3.8 ### SeaTunnel Config ```conf none ``` ### Running Command ```shell none ``` ### Error Exception ```log ErrorCode:[JDBC-04], ErrorDescription:[Connector database failed] - open() failed.errCode = 2, detailMessage = Unknown column 'create_time' in 'table list' at…… ``` ### Zeta or 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]
