[
https://issues.apache.org/jira/browse/HIVE-16297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vihang Karajgaonkar updated HIVE-16297:
---------------------------------------
Attachment: HIVE-16297.03.patch
Had a discussion with [~aihuaxu] and he thinks it will be better if we stick to
one approach which we have already in the source code to redact sensitive
information from the configs. The current approach is replace the sensitive
keys with EMPTY strings. Re-using existing methods instead. [~aihuaxu] can you
please review the latest patch?
> Improving hive logging configuration variables
> ----------------------------------------------
>
> Key: HIVE-16297
> URL: https://issues.apache.org/jira/browse/HIVE-16297
> Project: Hive
> Issue Type: Improvement
> Reporter: Vihang Karajgaonkar
> Assignee: Vihang Karajgaonkar
> Attachments: HIVE-16297.01.patch, HIVE-16297.02.patch,
> HIVE-16297.03.patch
>
>
> There are a few places in the source-code where we use
> {{Configuration.dumpConfiguration()}}. We should preprocess the configuration
> properties before dumping it in the logs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
