Skip to content
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

Build: Define strict version for Flink / Jackson / Hive2 / Tez 0.8 #9484

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

nastra
Copy link
Contributor

@nastra nastra commented Jan 16, 2024

When running into this issue, the build used Flink 1.18.0. I've noticed that we were silently using Flink 1.18.1 because a new patch version was just released, which caused a test to fail. This is because of how strictly and prefer (or even require) version definitions work.
According to https://docs.gradle.org/current/userguide/rich_versions.html Gradle would select a patch version as long as it matches the version range defined in strictly, which isn't necessarily what we want for those libraries.
I've changed them all to not use version ranges.

@nastra nastra force-pushed the gradle-strict-version-def branch from 94c7f3d to 5ceb69b Compare January 17, 2024 07:36
@nastra nastra requested review from aokolnychyi and pvary January 17, 2024 07:37
When running into this issue, the build used Flink 1.18.0.
I've noticed that we were silently using Flink 1.18.1 because a new patch version was just released, which caused a test to fail.
This is because of how `strictly` and `prefer` (or even `require`)
version definitions typically work.
According https://docs.gradle.org/current/userguide/rich_versions.html
Gradle would select a patch version as long as it matches the version
range defined in `strictly`, which isn't necessarily what we want for
those libraries.
I've changed them all to not use version ranges.
@nastra nastra force-pushed the gradle-strict-version-def branch from 5ceb69b to 78079a6 Compare January 17, 2024 07:38
Copy link
Contributor

@pvary pvary left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 pending tests

@amogh-jahagirdar
Copy link
Contributor

Yeah I think pinning these specific versions for these dependencies is a good idea. Silently pulling in newer dependencies and trying to debug why some test is failing is never fun. It becomes much easier to debug when we explicitly are changing the version since we know the change that is being made.

@amogh-jahagirdar amogh-jahagirdar merged commit b6cefe5 into apache:main Jan 18, 2024
41 checks passed
@nastra nastra deleted the gradle-strict-version-def branch January 19, 2024 07:05
adnanhemani pushed a commit to adnanhemani/iceberg that referenced this pull request Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants