Migrating GraphDB Configurations

To migrate from one GraphDB version to another, follow the instructions in the last column of the table below, and then the steps described further down in this page.

Compatibility between the versions of GraphDB, Connectors, and third party connectors

GraphDB and RDF4J

Connectors: Elasticsearch, Lucene, Solr

Steps for migrating from an older version

GDB

RDF4J

Con

ES

Luc

Solr

9.7.x

3.6.1

14.0.0

7.9.2

8.6.3

8.6.3

No special attention needed.

9.6.x

3.5.1

13.0.1

7.9.2

8.6.3

8.6.3

No special attention needed.

9.5.x

3.4.4

13.0.0

7.9.2

8.6.3

8.6.3

Introduced Entity change plugin (used by the Ontotext Platform) as part of the fingerprint. In a cluster, this will lead to out of sync for the workers. Stop the master and rename the txLog for backup purposes. Start the master again.

The following authentication parameters have been deprecated, but still work: graphdb.auth.module, graphdb.auth.kerberos.enabled

9.4.x

3.3.1

12.1.x

7.7.0

8.5.1

8.5.1

No special attention needed.

9.3.x

3.2.0

12.1.x

7.7.0

8.5.1

8.5.1

Recreate all connectors with the repair option.

9.2.x

3.2.0 -M1

12.0.x

7.3.1

8.2.0

8.2.0

Language tags in literals are now returned according to the recommended case normalization specified by BCP47, Section 2.1.1. For comparing language literals we recommend the SPARQL 1.1 langMatches function instead of comparing language tags directly (e.g. FILTER(lang(?var) = "en-gb") would fail because lang(?var) will return the case-normalized tag as en-GB).

Some aggregate queries may return different results due to a fix in RDF4J.

9.1.x

3.0.1

12.0.1

7.3.1

8.2.0

8.2.0

Introduced History plugin as part of the fingerprint. In a cluster, this will lead to out of sync for the workers. Stop the master and rename the txLog for backup purposes. Start the master again.

9.0.x

2.5.2

12.0.0

7.3.1

8.2.0

8.2.0

Recreate all connectors with the repair option.

8.11.x

2.5.2

11.0.0

6.6.x

7.7.x

7.7.x

No special attention needed.

8.10.x

2.5.2

11.0.0

6.6.x

7.7.x

7.7.x

No special attention needed.

8.9.x

2.4.6

10.1.0

6.6.x

7.7.x

7.7.x

Removal of SPARQL-MM from the fingerprint. In a cluster, this will lead to out of sync for the workers. Stop the master and rename the txLog for backup purposes. Start the master again.

8.8.x

2.4.2

10.0.0

6.3.x

7.4.x

7.4.x

No special attention needed.

8.7.x

2.3.2

9.0.0

6.3.x

7.4.x

7.4.x

Recreate all the connectors with the repair option. Need to rebuild Semantic similarity search indexes.

8.6.x

2.3.2

8.0.0

6.2.x

7.2.x

7.2.x

Need to rebuild GeoSPARQL index.

8.5.x

2.2.4

7.2.0

5.3.x

6.5.x

6.5.x

No more system repository in future installations. During the upgrade procedure, system repository will be removed while the data insight will be backed up. There will be a config.ttl file in each repository directory with config data. Important points:

  • Cannot query System repo.

  • More strict parser - IRI validation according to RFC3987.

8.4.x

2.2.2

7.2.0

5.3.x

6.5.x

6.5.x

Autocomplete is no longer part of the fingerprint. In case of cluster, this will lead to out of sync for the workers. Stop the master and rename the txlog for backup purposes. Start the master again.

8.3.x

2.2.2

7.1.0

5.3.x

6.5.x

6.5.x

No special attention needed.

8.2.x

2.2.1

7.0.0

5.3.x

6.5.x

6.5.x

No special attention needed.

8.1.x

2.1.6

6.0.2

2.4.0

6.2.1

6.2.1

Recreate all the connectors with the repair option. Please note the breaking changes for each connector:

8.0.x

2.0.3

6.0.2

2.4.0

6.2.1

6.2.1

No special attention needed.

Important points:

  • The engine replaces PCSO and PCOS indexes with CPSO.

  • Remove the owlim-license parameter from the repository TTL configuration.

For older versions, please ask for support.

Migrating a repository

If you want to migrate your GraphDB configurations and replicate the setup, there are three steps that you need to follow:

  1. Back up your repository by copying the binary image (explained in more detail here), or restore it from an RDF export or from a binary image or zip backup (explained in more detail here).

For steps 2 and 3, it is useful to know that the GraphDB distribution package consists of several folders that are described in detail here.

  1. Copy the conf directory to the new instance. It contains the logback and the GraphDB configuration.

  2. Copy the work directory to the new instance. It contains all Workbench-related details, e.g., saved queries, users, user roles, etc.

Migrating a cluster

No cluster support in GraphDB Free.

Migrating connectors and plugins

Lucene: All you need to do is recreate the connector. If new properties are introduced, they will have default values.

Autocomplete: The index will be disabled to keep the cluster healthy, so you will need to enable it in the Workbench.

RDF Rank: You need to compute the rank as it will be outdated. This can be done through the Workbench interface.