LZ4 missing dependency error after upgrading to 1.11.0

[cclp94]

Hello, after upgrading the driver to the latest version (coming from version 1.9.0), we noticed the new "lenient" check for LZ4 mentioned in previous issues. I followed the conversation on other threads, but was unable to determine if LZ4 is really a mandatory dependency or not. If it is, should it be installed as a peer dependency in my codebase?

Here is the error we see:

LZ4 module not installed: Missing dependency Error: Cannot find module '../build/Release/xxhash'
Require stack:
- /app/backend/node_modules/lz4/lib/utils.js
- /app/backend/node_modules/lz4/lib/static.js
- /app/backend/node_modules/lz4/lib/lz4.js
- /app/backend/node_modules/@databricks/sql/dist/utils/lz4.js
- /app/backend/node_modules/@databricks/sql/dist/utils/index.js
- /app/backend/node_modules/@databricks/sql/dist/result/ArrowResultHandler.js
- /app/backend/node_modules/@databricks/sql/dist/DBSQLOperation.js
- /app/backend/node_modules/@databricks/sql/dist/DBSQLSession.js
- /app/backend/node_modules/@databricks/sql/dist/DBSQLClient.js
- /app/backend/node_modules/@databricks/sql/dist/index.js
- /app/backend/api/dist/common/src/core/DatabricksClient.js

[shivam2680]

The error you're seeing is most likely not about LZ4 being missing, but about LZ4 being incompletely/incorrectly installed for your platform.

Answering your question:

• Is LZ4 mandatory? No, it's optional, but recommended for performance
• Should it be a peer dependency? No, it's correctly configured as an optional dependency. The driver handles its absence gracefully by disabling compression negotiation with the server

[cclp94]

Just found #300 . So I guess this has already been flagged and resolved. I'll be waiting for the next release when it comes. any ETA?

I'm in a similar situation as the other issue. Our API runs on node-alpine so the system doesn't have LZ4 at all

[samikshya-db]

This has been fixed and released. Feel free to re-open if you see any issue on this