[
https://issues.apache.org/jira/browse/AIRFLOW-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16832358#comment-16832358
]
ASF subversion and git services commented on AIRFLOW-2463:
----------------------------------------------------------
Commit c4daf707e3256667791635f7f38c43a27ec3d32a in airflow's branch
refs/heads/v1-10-stable from r-richmond
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=c4daf70 ]
[AIRFLOW-4434] Support Impala with the HiveServer2Hook (#5206)
Fix support for impala in hive hook through a config option
that turns off set variable commands. Breaking changes were
introduced in [AIRFLOW-2463].
(cherry picked from commit 0ae15d84b7d2aee4119a7432578b4431b13a08ee)
> Make task instance context available for hive queries
> -----------------------------------------------------
>
> Key: AIRFLOW-2463
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2463
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Kevin Yang
> Assignee: Kevin Yang
> Priority: Major
> Fix For: 1.10.2
>
>
> Currently hive queries run through HiveOperator() would receive task_instance
> context as hive_conf. But the context is not available when
> HiveCliHook()/HiveServer2Hook() was called through PythonOperator(), nor
> available when hive cli was called in BashOperator() nor available when
> HiveServer2Hook() was called in any operator.
> Having the context available would provide users the capability to audit hive
> queries.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
