[
https://issues.apache.org/jira/browse/HIVE-9974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergio Peña updated HIVE-9974:
------------------------------
Attachment: HIVE-9974.1.patch
Here's the patch.
There was one left method where needed the data redaction. Because execute() is
executed after compileInternal(), then we just get the query already redacted
from the conf variable.
> Sensitive data redaction: data appears in name of mapreduce job
> ---------------------------------------------------------------
>
> Key: HIVE-9974
> URL: https://issues.apache.org/jira/browse/HIVE-9974
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Attachments: HIVE-9974.1.patch
>
>
> Set up a cluster, configured a redaction rule to redact "B0096EZHM2", and ran
> Hive queries on the cluster.
> Looking at the YARN RM web UI and Job History Server web UI, I see that the
> mapreduce jobs spawned by the Hive queries have the sensitive data
> ("B0096EZHM2") showing in the job names:
> e.g., "select product, useri...product='B0096EZHM2'(Stage"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
