[
https://issues.apache.org/jira/browse/IGNITE-23284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Iurii Gerzhedovich updated IGNITE-23284:
----------------------------------------
Fix Version/s: 3.0
> SQL text in server logs on errors
> ---------------------------------
>
> Key: IGNITE-23284
> URL: https://issues.apache.org/jira/browse/IGNITE-23284
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 3.0
> Reporter: Alexander Belyak
> Assignee: Iurii Gerzhedovich
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> # start and init 1 node cluster
> # execute query: *select count(*) from users where login='alex' and
> password='123'*
> The problem is that server logs contain an error like:
> {code:java}
> 2024-09-26 08:57:05:391 +0000
> [INFO][%poc-tester-SERVER-172.24.1.2-id-0%sql-execution-pool-1][JdbcQueryEventHandlerImpl]
> Exception while executing query [query=select count(*) from users where
> login='alex' and password='123']
> org.apache.ignite.sql.SqlException: IGN-SQL-4
> TraceId:deb3621b-1ecf-49b1-a072-fc77ddbf579b Failed to validate query. From
> line 1, column 22 to line 1, column 26: Object 'USERS' not found
> {code}
> If the user's application retries the query on any error it'll lead to log
> overflow and rotation. It makes logs useless for DBA.
> Also, it's not safe to log query text, it could contain sensitive information.
> Let's move messages like this (low priority messages with well known user
> errors like a bad query) into a separate log files to let them rotate
> individually.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
