github-actions[bot] commented on issue #16046: URL: https://github.com/apache/dolphinscheduler/issues/16046#issuecomment-2122056337
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened   ### What you expected to happen TIME TYPE is setted String, execute sql as String, not Time, there will be an error when execute this sql. When the front-end SQL custom parameter is of type TIME, when it is passed to the back-end to set the parameter type for SQL execution, the Time type will be set to String, which will cause a type mismatch and an error when subsequent SQL is executed. ### How to reproduce It’s easy to reproduce when setting self-define param type TIME. When setting the custom parameter type during SQL execution to TIME, an error will occur when the back-end execution engine specially adapts to this type. ### Anything else _No response_ ### Version dev ### 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]
