1.12.0

What's Changed

• Support for session parameters (#307 by @sreekanth-db)
• Add metric logging for cloud fetch (#305 by @shivam2680)

Full Changelog: 1.11.0...1.12.0

1.11.0

What's Changed

• Enable cloud fetch by default by @shivam2680 in #287
• Added useLZ4Compression in ExecuteStatementOptions making compression configurable by @shivam2680 in #288
• Improve handling of extra / in URLs by @vikrantpuppala in #290
• Add thrift protocol version handling for driver features by @shivam2680 in #292
• Cleanup fields as they might be deprecated/removed/change in the future by @vikrantpuppala in #295
• Add lenient LZ4 check to handle dependecy errors gracefully. by @samikshya-db in #298

New Contributors

• @vikrantpuppala made their first contribution in #290
• @samikshya-db made their first contribution in #298

Full Changelog: 1.10.0...1.11.0

1.10.0

What's Changed

• renamed clientId to userAgentHeader in connect args by @shivam2680 in #281
• Give warning for deprecated clientId param by @shivam2680 in #282

New Contributors

• @shivam2680 made their first contribution in #278

Full Changelog: 1.9.0...1.10.0

1.9.0

What's Changed

• Fix: Fix the type check in polyfills.ts by @kravets-levko in #254
• Allow any number type by @kravets-levko in #255
• Support iterable interface for IOperation by @kravets-levko in #252
• Support streaming query results via Node.js streams by @kravets-levko in #262
• Add custom auth headers into cloud fetch request by @jackyhu-db in #267
• Support OAuth on databricks.azure.cn by @jackyhu-db in #271

Full Changelog: 1.8.4...1.9.0

1.8.4

• Fix: proxy agent unintentionally overwrites protocol in URL (#241)
• Improve Array.at/TypedArray.at polyfill (#242 by @barelyhuman)
• UC Volume ingestion: stream files instead of loading them into memory (#247)
• UC Volume ingestion: improve behavior on SQL REMOVE (#249)
• Expose session and query ID (#250)
• Make lz4 module optional so package manager can skip it when cannot install (#246)

Full diff: 1.8.3...1.8.4

1.8.3

• Improved retry behavior (#230)
• Fix: in some cases library returned too many results (#239)

Full diff: 1.8.2...1.8.3

1.8.2

Improved results handling when running queries against older DBR versions (#232)

Full diff: 1.8.1...1.8.2

1.8.1

This is a security release which addresses issues with library dependencies

https://github.com/databricks/databricks-sql-nodejs/security/dependabot/34

An issue in all published versions of the NPM package ip allows an attacker to execute arbitrary code and
obtain sensitive information via the isPublic() function. This can lead to potential Server-Side Request
Forgery (SSRF) attacks. The core issue is the function's failure to accurately distinguish between
public and private IP addresses.

1.8.0

• Retry failed CloudFetch requests (#211)
• Fixed compatibility issues with Node@14 (#219)
• Support Databricks OAuth on Azure (#223) @jackyhu-db
• Support Databricks OAuth on GCP (#224)
• Support LZ4 compression for Arrow and CloudFetch results (#216)
• Fix OAuth M2M flow on Azure (#228)

Full diff: 1.7.1...1.8.0

OAuth on Azure

Some Azure instances now support Databricks native OAuth flow (in addition to AAD OAuth). For a backward
compatibility, library will continue using AAD OAuth flow by default. To use Databricks native OAuth,
pass useDatabricksOAuthInAzure: true to client.connect():

client.connect({
  // other options - host, port, etc.
  authType: 'databricks-oauth',
  useDatabricksOAuthInAzure: true,
  // other OAuth options if needed
});

Also, we fixed issue with AAD OAuth when wrong scopes were passed for M2M flow.

OAuth on GCP

We enabled OAuth support on GCP instances. Since it uses Databricks native OAuth,
all the options are the same as for OAuth on AWS instances.

CloudFetch improvements

Now library will automatically attempt to retry failed CloudFetch requests. Currently, the retry strategy
is quite basic, but it is going to be improved in the future.

Also, we implemented a support for LZ4-compressed results (Arrow- and CloudFetch-based). It is enabled by default,
and compression will be used if server supports it.

1.7.1

This release contains a fix for the "Premature close" error which happened due to socket limit when intensively using library (#217)

Full diff: 1.7.0...1.7.1