-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lz4 dependency causes intermittent build failures #266
Comments
Is the lz4 dependency truly optional? Will the databricks client work without it? |
It doesn't look truly optional to me—I don't have a repro case for this, nor do I know under exactly what conditions it's significant; but from inspection it looks like the client will just fail if it gets an LZ4 compressed response but the databricks-sql-nodejs/lib/result/ArrowResultHandler.ts Lines 29 to 31 in 56bd0d9
That doesn't feel "truly optional"—it would be one thing if it gracefully fell back to a less performant JS implementation or something, but… |
@haggholm the fragment you shared is intended to show meaningful error if something went really bad. In fact, databricks-sql-nodejs/lib/utils/lz4.ts Lines 1 to 16 in 56bd0d9
Then, server is asked to return compressed results only if databricks-sql-nodejs/lib/DBSQLSession.ts Line 205 in 56bd0d9
|
Originally shared in #245, but that issue was resolved by making the dependency optional (with reduced functionality if omitted). However, lz4 can cause install problems in another way on systems that do have all the dependencies, s.t. NPM attempts to build it, but fails. We have a CI pipeline that usually passes but occasionally fails. We have not yet invested any time into investigating this, but I'm sharing it as a kind of warning sign.
It's worth noting that the LZ4 repository
so it's a dependency that's both known to be broken and unlikely to be fixed.
The text was updated successfully, but these errors were encountered: