NeufHuang opened a new issue, #16915: URL: https://github.com/apache/dolphinscheduler/issues/16915
### 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 When using the SQL node, several situations have been found that prevent saving: - Using CASE WHEN statements within aggregate functions, e.g., `` SUM(CASE WHEN ... THEN ... END)`` .  But the format `` max(case 1 when 1 then 2 end)`` can be saved normally - When the SQL includes the aggregate function `` GROUP_CONCAT()`` , see issue #14132 .  - Formatting, see issue #15559 .  The same SQL statement in the following format can be saved.  Deployed on Kubernetes, both 3.1.x and 3.2.x have these issues. I hope this issue can be resolved soon. Thank you! ### What you expected to happen If there is no risk of SQL injection, then regardless of the format, it should be saved normally. ### How to reproduce As above. ### Anything else _No response_ ### Version 3.1.x ### 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]
