[ https://issues.apache.org/jira/browse/AIRFLOW-4791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868989#comment-16868989 ]
ASF subversion and git services commented on AIRFLOW-4791: ---------------------------------------------------------- Commit 8a89175ad938ef1c3200384d1ed48105b61c64de in airflow's branch refs/heads/master from Jake Gysland [ https://gitbox.apache.org/repos/asf?p=airflow.git;h=8a89175 ] AIRFLOW-4791 add "schema" keyword arg to SnowflakeOperator (#5415) * added role, schema and warehouse added addition connection params - current hook does not allow for connecting with correct role ie security. current hook requires full qualification of database.schema.table_name in query - we should have the ability to have per schema/database connections in Airflow * added extra connection paramaters to operator Added role, warehouse and database parameters to the operator. Currently unable to use operator without qualifying the database.schema.table_name in the sql statement. Proper security is not applied if user id belongs to multiple roles, so roles is not defined when connecting. * AIRFLOW-4791 readability * AIRFLOW-4791 add to (and improve) docstring > SnowflakeOperator doesn't support schema argument > ------------------------------------------------- > > Key: AIRFLOW-4791 > URL: https://issues.apache.org/jira/browse/AIRFLOW-4791 > Project: Apache Airflow > Issue Type: Improvement > Components: contrib, hooks, operators > Affects Versions: 1.10.3 > Reporter: Jake Gysland > Priority: Major > > {{airflow.contrib.snowflake_operator.SnowflakeOperator}} doesn't provide a > way to set the schema to use for the connection. > There was a [PR opened on > [Github|https://github.com/apache/airflow/pull/4306] that added this, but the > committer didn't make a Jira ticket or complete the PR message template > correctly, and the PR was later closed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)