airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-343) Schema setting not propagated in HiveServer2Hook
Date Wed, 16 Nov 2016 05:23:58 GMT


ASF subversion and git services commented on AIRFLOW-343:

Commit 448e06f697589de5bc19f3af76f736ae043a6e6b in incubator-airflow's branch refs/heads/master
from [~gr8outdoors]
[;h=448e06f ]

[AIRFLOW-343] Fix schema plumbing in HiveServer2Hook

Allow HiveServer2Hook to be used on other databases than default.

Testing Done:
- Added new unit test coverage in HiveOperator to
cover these changes.  (This is the established
testing norm for HiveHook).

Closes #1743 from gr8routdoors/airflow_343

> Schema setting not propagated in HiveServer2Hook
> ------------------------------------------------
>                 Key: AIRFLOW-343
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>    Affects Versions: Airflow 2.0, Airflow 1.8, Airflow 1.7.1
>            Reporter: Devon Berry
> Although methods like #get_results, #get_records, and #get_pandas_df allow you to specify
a schema, the underlying delegate #get_conn does not support setting the schema:
> This story is to fix the wiring so that schema can be overridden.

This message was sent by Atlassian JIRA

View raw message