Repository navigation
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Feature Description
Currently, it seems impossible to set a custom timeout when connecting through the
mssqlconnector.When I have a query running more than 15000 ms, I get the following response when running
npm run sources:The
mssqlconnector uses npm packagemssqlunder the hood.According to the npm docs, this package allows for setting custom
requestTimeoutandconnectionTimeout, which both default to15000ms.Looking at the
mssqlconnector source code, it seems there would be some opportunity for injecting customrequestTimeoutandconnectionTimeoutsomewhere here.I would suggest you just allow for a single
timeoutoption, which steers bothmssqltimeouts under the hood, while still defaulting to15000ms.Goal of Feature
Allow
mssqlusers 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.All reactions