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

[jira] [Created] (AIRFLOW-590) Set module parameter in Oracle hook

Gerard Toonstra created AIRFLOW-590:
---------------------------------------

             Summary: Set module parameter in Oracle hook
                 Key: AIRFLOW-590
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-590
             Project: Apache Airflow
          Issue Type: Improvement
          Components: hooks
            Reporter: Gerard Toonstra
            Priority: Trivial


The Oracle database has the possibility to specify the module that accesses the database and the action that this module is performing. This can be set through a write-only property immediately after the connection is made. 

By setting the module in the connection parameters under "extra_json", which is usually where the service_name and SID are also kept, every oracle hook that is run can then have the module specified automatically (if module is set).

Developers can then personally decide if they wish to set the "action" property in their operators or totally ignore it . 

The way this looks in the session view of Oracle is like this:

Before:

amsterdam	inactive	test_dag.py@myserver (TNS V1-V3)

After:

amsterdam	inactive	airflow

(or variations thereof, like "airflow@myserver", "airflow@datascience", etc.).




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