Release Notes

GraphDB release notes provide information about the features and improvements in each release, as well as various bug fixes. GraphDB’s versioning scheme is based on semantic versioning. The full version is composed of three components:


e.g., 9.11.2 where the major version is 9, the minor version is 11 and the patch version is 2.

Occasional versions may include a modifier after a hyphen, e.g., 10.0.0-RC1 to signal additional information, e.g., a test release (TR1, TR2 and so on), a release candidate (RC1, RC2 and so on), a milestone release (M1, M2 and so on), or other relevant information.


Releases with the same major and minor versions do not contain any new features. Releases with different patch versions contain fixes for bugs discovered since the previous minor. New or significantly changed features are released with a higher major or minor version.

GraphDB 10 includes the following components with their version numbers:

  • RDF4J

  • GraphDB Connectors

  • GraphDB Workbench

Their versions use the same semantic versioning scheme as the whole product, and their values are provided only as a reference.

GraphDB 10.3.3

Released: 14 September 2023


GraphDB 10.3.3 includes several bug fixes and improvements of cluster stability. We recommend everyone using the cluster to upgrade to this version.

Various third-party libraries were updated to address vulnerabilities and fixes.

Component versions







GraphDB Engine & Cluster

New features and improvements

  • GDB-8108 Reduce memory consumption of big repository reinitialization

Bug fixing

  • GDB-8752 Read queries are executed only on the Leader node due to a race condition

  • GDB-8720 Failing to start a transaction renders the cluster inoperative

GraphDB Distributions & Deployment

New features and improvements

  • GDB-8744 Update various libraries to address known vulnerabilities

GraphDB 10.3.2

Released: 1 September 2023


GraphDB 10.3.2 includes multiple bug fixes and improvements across different components. We recommend everyone to upgrade to this version.

Important bug fixes include several issues that improve the cluster stability, query evaluation with UNIONs, as well as bug fixes for the SHACL validation API introduced in 10.3.

Ontop was upgraded to the latest minor version, 5.1, which provides better support for connecting to some third-party data sources via SQL.

Various third-party libraries were updated to address vulnerabilities and fixes.

Component versions







GraphDB Engine & Cluster

New features and improvements

  • GDB-8696 Add all named graphs as part of the validation report for SHACL

  • GDB-8671 Upgrade Ontop to 5.1.0

Bug fixing

  • GDB-8695 Duplicates in SHACL validation results when using the validator REST API

  • GDB-8692 SHACL validator REST API does not work with sh:shapesGraph

  • GDB-8672 Regression in queries containing complex path with alternatives since 10.1

  • GDB-8647 Complex UNIONs do not return all results

  • GDB-8621 Suboptimal evaluation of UNION with PathAlternativePattern

  • GDB-8613 Cluster deadlock between transaction rollback and snapshot creation

  • GDB-8612 “OutOfMemoryError: unable to create native thread” error in cluster

  • GDB-8568 Cluster node cannot apply snapshot after unsuccessful verification of entry and rollback attempt

  • GDB-8561 SHACL validator REST API does not work with named graphs

GraphDB Workbench

Bug fixing

  • GDB-8610 Download As button in the SPARQL editor does not work when the query string is very large

GraphDB Connectors & Plugins

Bug fixing

  • GDB-8537 An error during update of Solr Connector parameters preserves some of the changes

GraphDB Distributions & Deployment

New features and improvements

  • GDB-8703 Update various libraries to address known vulnerabilities

Bug fixing

  • GDB-8731 Cannot use private image in Helm if global.registry is set to a non-empty value

GraphDB 10.3.1

Released: 10 August 2023


GraphDB 10.3.1 includes multiple bug fixes and improvements across different components. We recommend everyone to upgrade to this version.

Important bug fixes include several issues that improve the cluster stability, as well as a fix for the SHACL validation API introduced in 10.3.

Various third-party libraries were updated to address vulnerabilities and fixes.

Component versions







GraphDB Engine & Cluster

Bug fixing

  • GDB-8593 Transaction cache file is not cleared on abort request by the user

  • GDB-8584 Two cluster nodes go out of sync at the same time and cannot get in sync

  • GDB-8560 SHACL validator REST API order is switched around

  • GDB-8543 Out of sync node does not proxy the requests to the leader node

  • GDB-8536 GraphDB does not delete temporary files created by the inferencer

  • GDB-8534 Extend Prometheus metrics to include description and type of each metric

  • GDB-8518 Cluster node goes out of sync due to leader shutdown when leader tries to rollback the last received entry

  • GDB-8513 Cannot get repository size, when deleting a repository and re-creating it with the same name in a cluster setup

  • GDB-8511 The work directory of a temporary inferencer instance is the current directory of the Java process, which may lead to failing validation of custom rulesets on repository creation

  • GDB-8498 Performing a backup while another backup is still running will output the error message as a file over HTTP

  • GDB-8496 Cluster management operations should be disabled while a backup restore operation is running

  • GDB-8494 Cluster follower node cannot return to in-sync state if the leader node goes out of sync while the follower node is catching up

  • GDB-8478 Reduced log level verbosity related to message “Signature already used” when a cluster node changes IP

  • GDB-8462 Cluster node cannot provide snapshot because of blocked verification of entry

  • GDB-8449 Suboptimal optimization of specific combinations of SPARQL UNION and BIND or VALUES

  • GDB-8381 Nodes cannot catch up if added to the cluster right after a backup is restored

  • GDB-8358 Two running cluster nodes cannot elect leader in three-node cluster

  • GDB-8326 Cluster node cannot return to in-sync after another node is stopped

  • GDB-8088 “FAILED_PRECONDITION: Unable to process entry during snapshot recovery” error in cluster

  • GDB-8018 Cluster node goes out of sync upon data insert, after successful data replication of a repository with a billion statements

  • GDB-7999 Cluster node goes out of sync if transaction log truncate is requested while a similarity index is being created

  • GDB-7892 A cluster created during a single instance backup restore procedure results in a NullPointerException after the restore

GraphDB Workbench

Bug fixing

  • GDB-8369 Cluster View broken toast error about lack of user permissions

  • GDB-7642 The browser’s Back button fails to return the user back to the SPARQL view if the user navigated to viewing a resource

GraphDB Distributions & Deployment

New features and improvements

  • GDB-8574 Update various libraries to address known vulnerabilities

GraphDB 10.3.0

Released: 17 July 2023

Component versions







GraphDB 10.3 introduces several exciting new features. One notable addition is the integration of ChatGPT, a popular Large Language Model, which greatly assists users in comprehending SPARQL queries and results, while also providing a new mechanism to enrich their RDF data. The upgrade of Ontop to version 5 significantly reduces the time and effort required to construct a knowledge graph from existing data sources by bringing new features and support for popular data management platforms like Dremio, Databricks and Snowflake. Furthermore, upgraded versions of the Elasticsearch and Solr connectors, along with a new dedicated OpenSearch connector, offer users better flexibility for indexing and searching their data. Additionally, GraphDB 10.3 includes numerous other improvements and bug fixes, further enhancing the overall user experience and stability of the system.


Seamless integration with Large Language Models

GraphDB 10.3 features an innovative integration with ChatGPT, one of the most popular Large Language Models. This groundbreaking feature aims to revolutionize the way users interact with RDF and unlock its full potential for both newcomers and experienced users.

With the integration of ChatGPT, a powerful tool, users will now be able to delve into the world of RDF with greater ease and gain a deeper understanding of its capabilities. Whether you’re just starting out or have advanced knowledge, this integration empowers you to leverage ChatGPT’s capabilities and seamlessly integrate them with your RDF data to extract valuable insights.

One of the most significant aspects of this integration is the ability to explain queries and/or results with the assistance of ChatGPT. This feature ensures that users not only obtain accurate and relevant answers but also gain a comprehensive understanding of the underlying query logic and the significance of the obtained results. Such explanations foster a more informed decision-making process and empower users to extract maximum value from their RDF datasets.

Furthermore, GraphDB now provides the ability to pose generic questions to ChatGPT directly from SPARQL. By doing so, users can enrich their graphs and extract additional information from their data. This novel approach brings a new level of interactivity and intelligence to your RDF queries, opening up endless possibilities for knowledge discovery.

Integration with data management platforms

We understand that data projects often begin with existing information sources that employ non-semantic data models or are too large to be replicated. This can pose challenges for users and limit their confidence in building a robust knowledge graph from these sources.

To address this, we have made substantial advancements in integrating GraphDB with various external data sources, enabling seamless connectivity and simplifying knowledge graph construction. In particular, the upgrade to Ontop 5 brings expanded integrations with well-known platforms such as Dremio, Databricks, and Snowflake. These integrations have been carefully designed to streamline the process of incorporating data from these platforms into your knowledge graph.

By harnessing the power of GraphDB’s upgraded Ontop integration, users can now enjoy reduced time and effort when building their knowledge graphs. This means you can focus more on extracting insights and deriving value from your data, rather than struggling with complex data integration challenges.

Connectors for the world

We also understand that many of you rely heavily on external managed services such as Elasticsearch and Solr. In response to the growing demand and the need to upgrade to the latest major versions, we have upgraded the Elasticsearch and Solr connectors in GraphDB to the latest client versions. This ensures seamless compatibility and empowers you to leverage the advanced features and improvements offered by the latest major releases.

In addition, we have recognized the rising popularity of OpenSearch as an alternative to Elasticsearch. Since the two platforms have diverged substantially, we have taken a proactive approach to provide a dedicated implementation for OpenSearch. This dedicated connector implementation will enable you to seamlessly integrate OpenSearch into your GraphDB workflow, giving you greater flexibility and options for indexing and searching your data and all of the features of the Elasticsearch connector.

Stay up-to-date with the latest versions of third-party libraries

As a general strategy to offer a secure and reliable product, we strive to provide up-to-date versions of third-party libraries. This includes both features and bug fixes provided by the libraries and also addresses newly identified public vulnerabilities.

The RDF4J library in GraphDB was upgraded to 4.3.3 and brings a number of SHACL improvements and general bug fixes.

GraphDB Engine & Cluster

New features and improvements

  • GDB-8441 Allow access for ROLE_USER to the RPC address endpoint

  • GDB-8423 Allow access for ROLE_USER to the cluster node/group status endpoints

  • GDB-8339 Improve CLEAR GRAPH performance in repositories with a large number of inferred statements

  • GDB-8276 As a user, I want to have a drop-down with JDBC drivers for officially supported Ontop data sources

  • GDB-8223 As a user, I need to ask generic questions to ChatGPT from SPARQL

  • GDB-8222 As a user, I need to ask ChatGPT to explain SPARQL queries and/or query results

  • GDB-8141 As a user, I want to replace named graph faster

  • GDB-8128 Support multiple algorithms for signing OpenID/OAuth tokens (RS256, RS384, RS512, ES256, ES384, ES512, PS256, PS384, PS512)

  • GDB-8107 Validate nodes’ external URLs when creating a cluster

  • GDB-8106 As an administrator, I want to be able to specify nested roles claims for OAuth

  • GDB-8050 Implement PathAlternative to evaluate UNION generated by SPARQL path expressions

  • GDB-7924 Add automatic support for accelerated S3 buckets for backup/restore

  • GDB-7923 Stream cloud backup directly from a follower node, bypassing the leader

  • GDB-7919 As a user, I want to use Ontop 5 features in GraphDB

  • GDB-7431 SHACL support for sh:severity

  • GDB-7428 SHACL support for sh:message

  • GDB-7427 As a data architect, I want to have SPARQL capabilities in SHACL shapes

  • GDB-7425 As a data architect, I want to use complex paths in SHACL constraints - sequence paths and alternate paths

  • GDB-6641 As a user, I need to see the Ontop query log as part of the GraphDB logs

  • GDB-6640 As a user, I want to pass standard Ontop configurations on repository creation

  • GDB-6593 Create a SHACL Validator API for validating repositories/models/files

Bug fixing

  • GDB-8362 SHACL sh:pattern fails when used with quotes

  • GDB-8284 importrdf preload overestimates the amount of statements in JSON-LD

  • GDB-8199 Requesting explain plan via the Workbench does not work for DESCRIBE queries

  • GDB-8158 GraphDB stops working when trying to serialize a large RDF result as JSON-LD

  • GDB-8116 Cluster error “Transaction Failed, Repository in read-only mode”

  • GDB-8075 Attempting to create an Ontop repository with same ID as an existing repository may write files in the directory of the existing repository

  • GDB-8045 Executing certain queries against large data in a named graph will not register the query in query monitoring

  • GDB-7856 Detect cluster security settings mismatch when security is setup as startup param on one of the nodes

  • GDB-7828 Backup/restore for a repository should also include its similarity indexes

  • GDB-7512 SPARQL function apf:splitIRI should return IRI for the namespace

  • GDB-7351 SPARQL INSERT with federation does not appear in the running query/update list

  • GDB-7350 “Unkown record type: 83” error when reading data from Wikidata over SPARQL federation

  • GDB-5948 Using OPTIONAL + FILTER EXISTS pushes the optional to the last position in the query

GraphDB Workbench

New features and improvements

  • GDB-8437 Introduce a mechanism to shorten and expand error messages in the workbench

  • GDB-7640 Make the Ontop edit repository windows bigger and use a monospaced font

Bug fixing

  • GDB-8418 Properties containing secrets should not reveal the secrets in Help -> System information in the workbench

  • GDB-8416 Inconsistent language setting in Create Ontop repository view when language is switched in another browser tab

  • GDB-8395 Workbench throwing harmless console warnings about invalid JSON in missing map files

  • GDB-8282 Workbench SPARQL editor download error redirects to server error page

  • GDB-8209 When a user is logged in via OpenID + OAuth the workbench displays misleading roles

  • GDB-8100 UI language switch does not take effect immediately

  • GDB-6647 “Copy link” icon in SPARQL results cannot be clicked

GraphDB Connectors & Plugins

New features and improvements

  • GDB-7967 As a user, I want to integrate GraphDB with Solr 9.x

  • GDB-7965 As a user, I want to integrate GraphDB with OpenSearch 2.x

  • GDB-7962 As a user, I want to integrate GraphDB with Elasticsearch 8.x

  • GDB-7950 As a user, I need to create a Kafka connector instance on a large repository

Bug fixing

  • GDB-7894 Kafka connector producer does not recover gracefully from transaction timeouts (ProducerFencedException)

GraphDB Distributions & Deployment

New features and improvements

  • GDB-8445 Update various libraries to address known vulnerabilities

  • GDB-8333 Upgrade RDF4J to 4.3.3

  • GDB-7886 Update the list of all 3rd party libraries in the Ontotext license agreement

Bug fixing

  • GDB-8277 Fix users.js config file in the public Helm repository to use provisioningUsername from the values file instead of hardcoded value