You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Dan Davydov (JIRA)" <ji...@apache.org> on 2018/03/06 00:12:00 UTC
[jira] [Commented] (AIRFLOW-226) Create separate pip packages for
webserver and hooks
[ https://issues.apache.org/jira/browse/AIRFLOW-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387016#comment-16387016 ]
Dan Davydov commented on AIRFLOW-226:
-------------------------------------
I feel strongly (at least for hooks) that they should be moved out. Things like storing secrets in the Airflow database, hooks, etc. are convenient, but they are equivalent to plugins and should have their own owners and maintainers. It doesn't make sense to e.g. make the owner and expert of the HiveHook be a committer in this repo but they certainly should be the committer and maintainer of the HiveHook repo. Another point as to why it makes sense to decouple hooks and the core is that it doesn't scale to support backwards incompatible changes to all operators for the Airflow committers, we are effectively supporting many hooks which we have no domain knowledge of. Other systems such as Jenkins follow a similar plugin framework.
> Create separate pip packages for webserver and hooks
> ----------------------------------------------------
>
> Key: AIRFLOW-226
> URL: https://issues.apache.org/jira/browse/AIRFLOW-226
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Dan Davydov
> Priority: Minor
>
> There are users who want only the airflow hooks, and others who many not need the front-end. The hooks and webserver should be moved into their own packages, with the current airflow package depending on these packages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)