Enable creation of backwards-compatible extracts#1052
Merged
lonvia merged 2 commits intokomoot:masterfrom Apr 15, 2026
Merged
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Reviewed by Cursor Bugbot for commit e876860. Configure here.
e876860 to
e5d54ac
Compare
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.

As already mentioned in #1029 (comment), there is an issue with OpenSearch (OS) where OS databases are forward-compatible but not backwards. You can use a database created on an older version of the 3.x series with a newer minor version but not vise versa.
The database extracts on the download server are supposed to work for all releases in a major series of Photon. There simply is no bandwidth to create separate extracts for each minor release. So, in order to make that work, the extracts need to be created against the smallest used OS version in the major Photon release series.
To make that work and still get the newest available minor OS version with each Photon release, I've come up with the following plan: a) always keep the master branch on the latest OS 3.x version and also include these in releases. b) When making a release build a special version of Photon with the lower OS version (currently 3.5) and deploy that on the extract server. This gives us OS 3.5-compatible database extracts while everybody can run a Photon version with the latest and greatest (and securest) OS.
This PR adds two things to make that happen:
./gradlew assemble -PosVersion=3.5.0.0.