airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ace Haidrey (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRFLOW-788) Context unexpectedly added to hive conf
Date Tue, 31 Oct 2017 18:41:00 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227301#comment-16227301
] 

Ace Haidrey edited comment on AIRFLOW-788 at 10/31/17 6:40 PM:
---------------------------------------------------------------

Should we add an option in the HiveOperator to pass this or not? By default have it not pass
it


was (Author: ahaidrey):
Should we add an option in the HiveOperator to pass this or not?

> Context unexpectedly added to hive conf
> ---------------------------------------
>
>                 Key: AIRFLOW-788
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-788
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: hive_hooks
>            Reporter: Bolke de Bruin
>             Fix For: 1.9.0
>
>
> If specifying hive_conf to run_cli extra variables are added from the context, e.g. airflow.ctx.dag.dag_id
. 
> In secured environments this can raise the need for a configuration change as these variables
might not be whitelisted.
> Secondly one could regard it as information leakage, as its is added without the user's
consent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message