healchow opened a new issue, #6026:
URL: https://github.com/apache/inlong/issues/6026

   ### What happened
   
   Execute the `apache_inlong_audit_clickhouse.sql` error:
   
   ```sql
   5b142b25d12d :) SET NAMES utf8mb4;
   
   Syntax error: failed at position 11 ('utf8mb4'):
   
   SET NAMES utf8mb4;
   
   Expected one of: token, Dot, Equals
   ```
   
   ```sql
   5b142b25d12d :) SET FOREIGN_KEY_CHECKS = 0;
   
   SET FOREIGN_KEY_CHECKS = 0
   
   Query id: a79b41c4-f65e-44cf-a76d-bd49de02c293
   
   0 rows in set. Elapsed: 0.001 sec. 
   
   Received exception from server (version 22.1.3):
   Code: 115. DB::Exception: Received from localhost:9000. DB::Exception: 
Unknown setting FOREIGN_KEY_CHECKS. (UNKNOWN_SETTING)
   ```
   
   ```sql
   5b142b25d12d :) SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
   
   Syntax error: failed at position 16 ('"NO_AUTO_VALUE_ON_ZERO"'):
   
   SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
   
   Expected one of: TRUE, FALSE, literal, NULL, number, Bool, true, false, 
string literal
   ```
   
   ```sql
   5b142b25d12d :) SET time_zone = "+00:00";
   
   Syntax error: failed at position 17 ('"+00:00"'):
   
   SET time_zone = "+00:00";
   
   Expected one of: TRUE, FALSE, literal, NULL, number, Bool, true, false, 
string literal
   ```
   
   ### What you expected to happen
   
   Can execute successfully.
   
   ### How to reproduce
   
   Just execute the `apache_inlong_audit_clickhouse.sql`.
   
   ### Environment
   
   _No response_
   
   ### InLong version
   
   master
   
   ### InLong Component
   
   InLong Audit
   
   ### 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