Skip to content

HIVE-30017: Upgrade postgresql to 42.7.12 - #6751

Open
Akanksha-kedia wants to merge 2 commits into
apache:masterfrom
Akanksha-kedia:bump-postgresql-42.7.12
Open

HIVE-30017: Upgrade postgresql to 42.7.12#6751
Akanksha-kedia wants to merge 2 commits into
apache:masterfrom
Akanksha-kedia:bump-postgresql-42.7.12

Conversation

@Akanksha-kedia

Copy link
Copy Markdown

What changes were proposed in this pull request?

Bumps org.postgresql:postgresql from 42.7.3 to 42.7.12 in pom.xml and standalone-metastore/pom.xml.

This supersedes #6599, which targeted 42.7.11 for the same CVE and stalled because the original author lacked ASF JIRA credentials to proceed. Picking it up here at a newer patch version per the discussion on that PR.

Why are the changes needed?

Addresses the CVE affecting org.postgresql:postgresql versions >= 42.2.0, < 42.7.11 by moving to a later patched release.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Dependency version bump only; existing test suite covers usage.

cc @deniskuzZ @uros-b @pranitatiwari-per

Bumps org.postgresql:postgresql from 42.7.3 to 42.7.12 in both the
root pom.xml and standalone-metastore/pom.xml, superseding apache#6599
(which targeted 42.7.11 and stalled without ASF JIRA credentials to
merge).
ayushtkn
ayushtkn previously approved these changes Sep 2, 2026

@ayushtkn ayushtkn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM

@uros-b uros-b left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thank you @Akanksha-kedia!

@ayushtkn

ayushtkn commented Sep 3, 2026

Copy link
Copy Markdown
Member

@Akanksha-kedia there are test failures which are related can u check

TestBeelineArgParsing hardcoded the path to postgresql-42.7.3.jar in
the local Maven repo to test loading it as a local driver jar. Bumping
postgres.version to 42.7.12 meant that jar no longer exists at the
build's local repo location, failing the test in CI (flagged by
ayushtkn on Jenkins pr-head).

Passes postgres.version through as a system property (same pattern
already used for derby.version) and has the test build the jar path
from it instead of a hardcoded version string.
@Akanksha-kedia

Copy link
Copy Markdown
Author

@ayushtkn Found it — TestBeelineArgParsing hardcoded the path to postgresql-42.7.3.jar in the local Maven repo. Bumping postgres.version means that jar no longer exists at that path, so the test failed to find it. Pushed a fix that derives the path from postgres.version instead (same pattern as derby.version). Verified locally with mvn test -Dtest=TestBeelineArgParsing -pl beeline -am.

@sonarqubecloud

sonarqubecloud Bot commented Sep 3, 2026

Copy link
Copy Markdown

@Akanksha-kedia

Copy link
Copy Markdown
Author

@ayushtkn @uros-b @asf-ci-hive please help to review and merge

@Akanksha-kedia Akanksha-kedia changed the title Upgrade postgresql to 42.7.12 HIVE-30017: Upgrade postgresql to 42.7.12 Sep 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants