You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Large results sets consumed from query causes problems for tasks ( 1 , 2 )
I could not find any option to specify upper bound for query execution , ( sth like jdbc query timeout ) in source task configs?
Is there any specific reason for not including that option? It may be useful for applying fail fast behavior for tasks with heavy load results from query.
Regards
The text was updated successfully, but these errors were encountered:
Hi,
Large results sets consumed from query causes problems for tasks ( 1 , 2 )
I could not find any option to specify upper bound for query execution , ( sth like jdbc query timeout ) in source task configs?
Is there any specific reason for not including that option? It may be useful for applying fail fast behavior for tasks with heavy load results from query.
Regards
The text was updated successfully, but these errors were encountered: