-
Notifications
You must be signed in to change notification settings - Fork 167
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
SNOW-1023077: JDBC driver package is too big #1622
Comments
hi and thank you for raising this issue - also for sharing the support case #id. we're taking a look. |
the official support case has been closed, but there's some which we would like to share here in case it helps someone else too. The thin jar for the driver is still in experimental phase, and will be there for a while. At the same time, we thank you and everyone who adopted it so early and provided their feedback ! Based on those feedbacks and on existing plans, the development and optimization of the thin jar is still ongoing. Something which we already confirmed is not applicable for your case, but might be applicable for someone else while the development efforts are ongoing - you might be able to achieve smaller artifact size by excluding unused dependencies. <dependency>
<groupId>net.snowflake</groupId>
<artifactId>snowflake-jdbc-thin</artifactId>
<version>3.14.5</version>
<exclusions>
<exclusion>
<groupId>com.google.api</groupId>
<artifactId>gax</artifactId>
</exclusion>
<exclusion>
<groupId>com.google.cloud</groupId>
<artifactId>google-cloud-core</artifactId>
</exclusion>
<exclusion>
<groupId>com.google.cloud</groupId>
<artifactId>google-cloud-storage</artifactId>
</exclusion>
<exclusion>
<groupId>com.microsoft.azure</groupId>
<artifactId>azure-storage</artifactId>
</exclusion>
<!-- <exclusion>-->
<!-- <groupId>com.amazonaws</groupId>-->
<!-- <artifactId>*</artifactId>-->
<!-- </exclusion>-->
</exclusions>
</dependency> We'll keep this thread posted and you can also watch the official release notes for the JDBC driver for updates. |
Thanks @sfc-gh-dszmolka , do we have any update for the driver size? We recently have an issue caused by the driver size as well. If not, we plan to use older version to reduce the package size. |
hi - no specific update besides the above; which can be used to potentially reduce the size of the artifact in the thin jar. |
Thanks for your comment @sfc-gh-dszmolka , really appreciated! We tried thin jar and will work around by excluding certain dependencies from the jar file. |
On a side note, why did the size of the JAR more than doubled between 3.13 and 3.14 ? |
Hey team 👋🏻 I've recently had an issue with updating to the latest version of jdbc-driver (v3.2.0) because of how large the jar is, and it exceeding the lambda package deployment size. I want to use the thin jar, but according to the release notes it is experimental. Is there a reason it's still experimental? |
hey - we have plans to make it non-experimental by the end of this year - January 2025. Until then, you're more than free to test the thin jar in your project; and see how it works out for you. |
Thanks for the prompt reply @sfc-gh-dszmolka, will give it a go 👍🏻 |
Snowflake account identifier:
FZLBQHX.CW96174
(See ticket 00686664 for more data and context)Hello,
We are having issues with the size of the jars, despite the use of the new experimental thin-jar #1554 (comment).
Indeed, we are packaging our application to PyPi , and there is a default size limit of 60 MB to avoid any abuse.
We are having some issues with the Snowflake jar sizes:
The size reduction of the thin jar is only apparent, as the driver itself is still 65 MB. You can see it when creating a dummy project with the following
pom.xml
:and then run
mvn package
anddu -h target/fat-standalone.jar
Running the same with version 3.13.30 yields 32 MB only!
Side note: we encounter the issue on PyPi, but there are size constraints in other places, such as (based on the issues filed on the Snowflake repository):
This issue prevents us from picking the latest version for bug fixes and new features
The text was updated successfully, but these errors were encountered: