You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2016/06/10 23:08:20 UTC

[jira] [Commented] (AIRFLOW-235) Improve connectors interface

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

Chris Riccomini commented on AIRFLOW-235:
-----------------------------------------

+1

There actually *is* a way to do this, and both the JDBC and Google cloud platform connectors actually take advantage of it. It's completely undocumented, though, and a bit of a hack. It also requires hard-coding stuff in the core of Airflow that's specific to contrib hooks in some cases.

> Improve connectors interface
> ----------------------------
>
>                 Key: AIRFLOW-235
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-235
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: webserver
>    Affects Versions: Airflow 1.7.1.2
>            Reporter: Jakob Homan
>
> Right now the connections interface has the same fields for all connectors, whether or not they apply.  Per-connector values are stuffed into the extra field, which doesn't have any description or clarification.  Connectors don't have any way of displaying what extra information they require.
> It would be better if connectors could define what fields they specified through the interface (a map of field name to type, description, validator, etc).  The connector web page could then render these and pass them back to the connector when it is instantiated. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)