Nexus Repository Database
Nexus Repository has two databases available. Use the following table to choose a database for your deployment.
See configure PostgreSQL for new instances
See migrating to a PostgreSQL for existing instances
Database | Appropriate For |
|---|---|
External PostgreSQL (Preferred) | The following features are only available for PostgreSQL deployments.
|
Embedded H2 |
Nexus Repository instances used beyond these levels may become unstable. Sonatype is not able to guarantee support for your deployment beyond these limits. |
Legacy Orient Database
Nexus Repository's legacy embedded OrientDB database is in extended maintenance as of August 2024. Nexus Repository deployments must migrate off of OrientDB.
You must remain on the 3.70.x version line if you are unable to migrate at this time.
The migration from Orient's NoSQL database to PostgreSQL has introduced fundamental changes in the external behavior of Nexus Repository.
Features not supported for PostgreSQL The Legacy high availability clustering (HA-C) and community formats are not supported for PostgreSQL environments.
The Bower format has been removed.
External plugins will not work External plugins that introduce new repository types, interact with repository content, or interact with the database directly need to be updated to accommodate the PostgreSQL database.
Backup and restore Existing OrientDB backups are not compatible with PostgreSQL and there is no similar task for backing up the PostgreSQL database in Nexus Repository.
Logging Logging related to database interactions is different.
Asset paths require a forward slash The asset name matchers are interpreted differently. Regular expressions are no longer anchored by default meaning that results are different for cleanup policies and asset references using the API. References to assets require a forward slash in front of a path to work.
Groovy scripting is not recommended Groovy scripts accessed undocumented Nexus Repository APIs that need to be updated to work. For both security and forward compatibility reasons, we recommend making use of the public REST API as much as possible rather than using Groovy scripting.
Coordinate-based content selectors Content selectors that use coordinates are deprecated in PostgreSQL and are no longer supported.
Changes impacting webhooks events When performing component cleanup, Nexus Repository no longer generates DELETED events for each component and assets deleted during component cleanup. Instead, there is an event of type PURGED containing the IDs of all deleted assets and components. More events of type UPDATED are generated during repository uploads.
Major Changes to Asset Name Matcher Regular Expressions
Regular expressions used in cleanup policies for path and name matching are handled differently when queried in Orient than in other environments. More content may be removed from repositories during cleanup.
Anchored queries match the entire asset name when there isn’t a wildcard in the regex.
In Orient, the Asset Name Matcher uses Lucene regular expressions that are anchored by default.
H2 and PostgreSQL environments use Java regular expressions that are not anchored.
Example of an Expression That Matches More Items After Migration to PostgreSQL/H2
This example contains the following assets for consideration:
/antlr/antlr/2.7.2/antlr-2.7.2.jar /org/antlr/antlr-master/3.1.3/antlr-master-3.1.3.pom
A cleanup policy sets the Asset Name Matcher using the following regular expression.
antlr.*
Cleanup in OrientDB would only match the first item while H2 and Postgres queries will remove both components.