Repository navigation
Conversation
The cbdb-build images are where Apache Cloudberry PXF gets compiled, and
PXF's server build needs a full JDK. Not every image had one:
- ubuntu22.04 had only the Java 11 JRE that ca-certificates-java pulls
in, so no javac.
- ubuntu24.04 and ubuntu26.04 had no Java at all.
- rocky9 had JDK 11, while Rocky 9's default JDK is 17.
Install each distribution's default OpenJDK as a full JDK:
rocky8 java-11-openjdk-devel (unchanged)
rocky9 java-17-openjdk-devel (replaces JDK 11)
rocky10 java-21-openjdk-devel (unchanged)
ubuntu22.04 openjdk-11-jdk-headless
ubuntu24.04 openjdk-21-jdk-headless
ubuntu26.04 openjdk-25-jdk-headless (what default-jdk-headless
resolves to there)
Ubuntu gets the headless JDK; nothing in these images needs the GUI
libraries.
On rocky9, java and javac now resolve to 17 instead of 11, and
/usr/lib/jvm/java-11-openjdk is gone. Nothing in this repository uses
the image's JDK 11, PXF main builds with 17, and PXF 2.2 builds and
passes its server unit tests on 17.
Vlasdislav
reviewed
Nov 6, 2026
| libcgroup1 \ | ||
| meson \ | ||
| ninja-build \ | ||
| openjdk-11-jdk-headless \ |
Collaborator
There was a problem hiding this comment.
Why do we want 11?
Suggested change
| openjdk-11-jdk-headless \ | |
| openjdk-17-jdk-headless \ |
Member
Author
There was a problem hiding this comment.
For the PXF 2.x version, we support the openjdk-11/17/18. I want to use the default JDK version for each operating system. OpenJDK-11 is the default one in Ubuntu 22.04 software source.
For PXF 3.x (main), we ask the 17 at least. We have a set up on this. It will not affect the PXF CI.
leborchuk
approved these changes
Nov 6, 2026
leborchuk
left a comment
leborchuk
left a comment
Contributor
There was a problem hiding this comment.
LGTM, we need it to build pxf binaries
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The cbdb-build images are where Apache Cloudberry PXF gets compiled, and PXF's server build needs a full JDK. Not every image had one:
Install each distribution's default OpenJDK as a full JDK:
Ubuntu gets the headless JDK; nothing in these images needs the GUI libraries.
On rocky9, java and javac now resolve to 17 instead of 11, and
/usr/lib/jvm/java-11-openjdkis gone. Nothing in this repository uses the image's JDK 11, PXF main builds with 17, and PXF 2.2 builds and passes its server unit tests on 17.Fixes #ISSUE_Number
What does this PR do?
Type of Change
Breaking Changes
Test Plan
make installcheckmake -C src/test installcheck-cbdb-parallelImpact
Performance:
User-facing changes:
Dependencies:
Checklist
Additional Context
CI Skip Instructions