You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2024/01/09 11:32:00 UTC
[jira] [Assigned] (IGNITE-21055) Sql. ParserService should use SqlNode::unparse instead of SqlNode::toString
[ https://issues.apache.org/jira/browse/IGNITE-21055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Zhuravkov reassigned IGNITE-21055:
-----------------------------------------
Assignee: Maksim Zhuravkov
> Sql. ParserService should use SqlNode::unparse instead of SqlNode::toString
> ---------------------------------------------------------------------------
>
> Key: IGNITE-21055
> URL: https://issues.apache.org/jira/browse/IGNITE-21055
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Maksim Zhuravkov
> Assignee: Maksim Zhuravkov
> Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> Problem - SqlNodes may contain sensitive information that can leak into logs via toString method, in order to avoid such
> issues it maybe a good idea to override toString method to remove all sensitive information for such SQL nodes.
> Unfornutently such approach breaks PrepareService, because it builds a copy for a SQL AST from SQL string created by SqlNode::toString method.
> Let's update ParserService to build SQL via unparse method to avoid this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)