You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Tao Feng (JIRA)" <ji...@apache.org> on 2018/03/07 02:13:00 UTC

[jira] [Updated] (AIRFLOW-2183) Refactor DruidHook to able to issue arbitrary query to druid broker

     [ https://issues.apache.org/jira/browse/AIRFLOW-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tao Feng updated AIRFLOW-2183:
------------------------------
    Description: 
Currently the druidhook only maintains connection to overlord and is used solely for ingestion purpose. We would like to extend the hook so that it could be utilized to issue a query to druid broker. 

There are couples of benefits:
 # Allow any operator to issue query to druid broker.
 # Allow us later on to create a druid_checker for data quality validation purpose. 

  was:
Currently the druidhook only maintains connection to overlord and is used solely for ingestion purpose. We would like to extend the hook so that it could be utilized to issue a query to druid broker. 

There are couples of benefits:
 # Allow any operator to issue query to druid broker.
 # Allow us later on to create a druid_checker for data quality purpose. 


> Refactor DruidHook to able to issue arbitrary query to druid broker
> -------------------------------------------------------------------
>
>                 Key: AIRFLOW-2183
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2183
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Tao Feng
>            Assignee: Tao Feng
>            Priority: Major
>
> Currently the druidhook only maintains connection to overlord and is used solely for ingestion purpose. We would like to extend the hook so that it could be utilized to issue a query to druid broker. 
> There are couples of benefits:
>  # Allow any operator to issue query to druid broker.
>  # Allow us later on to create a druid_checker for data quality validation purpose. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)