custom timeout for mssql
connector
#2414
bvanderhorn
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Feature Description
Currently, it seems impossible to set a custom timeout when connecting through the
mssql
connector.When I have a query running more than 15000 ms, I get the following response when running
npm run sources
:The
mssql
connector uses npm packagemssql
under the hood.According to the npm docs, this package allows for setting custom
requestTimeout
andconnectionTimeout
, which both default to15000
ms.Looking at the
mssql
connector source code, it seems there would be some opportunity for injecting customrequestTimeout
andconnectionTimeout
somewhere here.I would suggest you just allow for a single
timeout
option, which steers bothmssql
timeouts under the hood, while still defaulting to15000
ms.Goal of Feature
Allow
mssql
users to run a query taking longer than 15s.Current Solution / Workarounds
This is breaking my current process.
Alternatives
Not sure for now. I've already optimised the heck out of my queries. Other connectors offer larger timeouts already. Take a look at
BigQuery
's 3,600,000 ms timeout.Beta Was this translation helpful? Give feedback.
All reactions