eladkal commented on code in PR #60689:
URL: https://github.com/apache/airflow/pull/60689#discussion_r2700972737


##########
providers/snowflake/src/airflow/providers/snowflake/hooks/snowflake_sql_api.py:
##########
@@ -78,6 +79,7 @@ class SnowflakeSqlApiHook(SnowflakeHook):
     :param token_renewal_delta: Renewal time of the JWT Token in timedelta
     :param deferrable: Run operator in the deferrable mode.
     :param api_retry_args: An optional dictionary with arguments passed to 
``tenacity.Retrying`` & ``tenacity.AsyncRetrying`` classes.
+    :param http_timeout_seconds: Optional timeout for http requests.

Review Comment:
   > so using a single generic kwargs dict would either add extra complexity or 
work well for only one of the two paths.
   
   can you explain the complexity?
   The way I see it you get a dic from user and you just pass it as parameter 
to the underlying library (whatever that may be). What am I missing?



##########
providers/snowflake/src/airflow/providers/snowflake/hooks/snowflake_sql_api.py:
##########
@@ -78,6 +79,7 @@ class SnowflakeSqlApiHook(SnowflakeHook):
     :param token_renewal_delta: Renewal time of the JWT Token in timedelta
     :param deferrable: Run operator in the deferrable mode.
     :param api_retry_args: An optional dictionary with arguments passed to 
``tenacity.Retrying`` & ``tenacity.AsyncRetrying`` classes.
+    :param http_timeout_seconds: Optional timeout for http requests.

Review Comment:
   > so using a single generic kwargs dict would either add extra complexity or 
work well for only one of the two paths.
   
   can you explain the complexity?
   The way I see it you get a dict from user and you just pass it as parameter 
to the underlying library (whatever that may be). What am I missing?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to