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
There is a connection per thread. If a connection already exists, it is reused and named with the new connection name (usually the unique_id of the node). I think it will be more clear in the modified ConnectionReused message.
Is this a new bug in dbt-core?
Current Behavior
The connection reused event does not show in the logs:
Re-using an available connection from the pool (formerly {self.conn_name})
I think this is because the connection reused event is never fired.
I am not completely sure if I am reading the code below correctly, but I think the
ConnectionReused
is misplaced and maybe never reached:I read the following
I do not understand why the connection reused event might be sent right after the new connection event is sent.
Also, I do not understand when this
conn.name == conn_name
evaluates toFalse
. When is a different connection name used within the same thread?Expected Behavior
Steps To Reproduce
NA
Relevant log output
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: