[
https://issues.apache.org/jira/browse/IGNITE-14441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311351#comment-17311351
]
Taras Ledkov commented on IGNITE-14441:
---------------------------------------
[~nizhikov]
Please take a look on the usage of the {{S#includeSensitive}}. The class names
and field names are hidden in log messages.
SQL queries and plans also contains names of the tables & fields and must be
hidden in log messages.
I guess the behavior of hiding sensitive info must be consistent.
I don't see any reason to hide SQL constants at the system views because user
may use parameters for sensitive info and access to system views must check
security permission.
> Query plan printed for long running query must use
> IGNITE_TO_STRING_INCLUDE_SENSITIVE policy
> --------------------------------------------------------------------------------------------
>
> Key: IGNITE-14441
> URL: https://issues.apache.org/jira/browse/IGNITE-14441
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
> Fix For: 2.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Query plan printed for long running query must use
> IGNITE_TO_STRING_INCLUDE_SENSITIVE policy.
> Now query parameters may be printed in the query plan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
