Release notes

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

major.minor.patch

e.g., 8.1.2 where the major version is 8, the minor version is 1 and the patch version is 2.

Note

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 8 includes two components with their version numbers:

  • RDF4J
  • GraphDB Connectors

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

GraphDB 8.2

Released: 20 June 2017

Component versions

RDF4J Connectors
2.2.1 7.0.0

Important

  • Simplified cluster configuration and easier administration with the new protocol using a single HTTP port for worker replications;
  • Quickly develop integration tests that configure a GraphDB cluster in memory via a standard exposed API. For more information check the example how to setup a cluster;
  • Major redesign of the Connectors with a more robust implementation better working in clusters under extreme read/write load and lagging workers
  • Improved Elasticsearch Connector speed for indexing large write transactions with the bulk API;
  • Upgrade to the latest RDF4J release and support for property-centric access to RDF models;
  • Many bugfixes in all database components;

GraphDB Engine

Features and improvements

  • GDB-986 - Return Server and X-Powered-By headers
  • GDB-1593 - Update rdf4j to 2.2.1

Bug fixes

  • GDB-1308 - IllegalStateException is thrown when trying to upload a .rj file
  • GDB-1489 - GraphDB Nagios plugin returns WARNING on ‘connection refuse’
  • GDB-1523 - Inconsistent sameAs results when switching between explicit, implicit and explicit/implicit views in Workbench
  • GDB-1635 - Parallel transaction fails with: org.eclipse.rdf4j.rio.RDFHandlerException: java.lang.ArrayIndexOutOfBoundsException: 1381524
  • GDB-1750 - Ruleset generating new blank nodes in the consequence part fails with “Connection in precommit state may not create IDs”

GraphDB Workbench

Features and improvements

  • GDB-1165 - Autocomplete should search by label also, not only iri local name
  • GDB-1607 - Add an option to use or not disable same as graph in the resource view for “implicit” and “implicit + explicit”
  • GDB-1630 - As a user I want to save Graph Visualization state and reload it later

Bug fixes

  • GDB-1528 - Explicit statements hides implicit statements in resource view
  • GDB-1646 - SPARQL editor: results are switched to table view when changing the workbench section
  • GDB-1671 - Display issue in cluster view with *.xip.io addresses
  • GDB-1684 - Muting the remote master mutes the local one instead
  • GDB-1685 - Workbench cluster view does not allow to peer master1 to master2 and master2 to master1
  • GDB-1774 - An unreachable inactive remote location prevents the Workbench from starting properly

GraphDB Cluster

Features and improvements

  • GDB-1703 - Convert cluster replication from standalone TCP server to the RDF4J HTTP server

Bug fixes

  • GDB-1246 - Local consistency HTTP header parameter is not respected by the cluster
  • GDB-1643 - Worker’s state may not update during replication or backup

GraphDB Connectors

Features and improvements

  • GDB-1428 - Upgrade Elasticsearch Connector to Elasticsearch 5.x
  • GDB-1429 - Upgrade Lucene Connector to Lucene 6.4
  • GDB-1430 - Upgrade Solr Connector to Solr 6.4
  • GDB-1636 - GDB-1634 Determine possible scenarios for partial updates and write tests
  • GDB-1650 - Increase the update speed of the Elasticsearch and SOLR Connectors by sending multiple documents per request

Bug fixes

  • GDB-1485 - Lagging worker, configured with a Connector with property chains, may fail in an out of sync state because of a wrong fingerprint compared to the test worker
  • GDB-1634 - Auto-sync mechanism of the connectors doesn’t work as expected in some partial chain updates
  • GDB-1652 - Object (nested) fields are shown as required in the Elasticsearch Connector options
  • GDB-1835 - Entity filter on graphs throws an exception if applied over nested fields
  • GDB-1836 - Allow fields starting with @ and do proper validation of nested field names