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.4.2

Released: 12 October 2018

Component versions

RDF4J Connectors
2.2.2 7.2.0

Important

  • Some non-critical bug fixes in the Engine.

GraphDB Engine

Bug fixes

  • GDB-2424 Inconsistent evaluation behaviour in a hanging query
  • GDB-2962 Cannot pass SPARQL variable bindings as HTTP query parameters in ClientHTTPTupleQuery

GraphDB 8.4.1

Released: 05 January 2018

Component versions

RDF4J Connectors
2.2.2 7.2.0

Warning

  • Fixed a critical bug in the engine (see GDB-2329). We advise all our users to migrate from 8.4.0 to 8.4.1 to avoid data corruption.

GraphDB Engine

Bug fixes

  • GDB-2329 - Random statements appear in the databases after multiple concurrent writes
  • GDB-2311 - Importing file with a lot of prefixes through master fails with RDFParseException: Unexpected end of file

GraphDB Cluster

Bug fixes

  • GDB-2256 - Read only master should lock worker statuses

GraphDB Workbench

Bug fixes

  • GDB-2009 - Repository info popup is displayed sometimes on non-home views if that is the first view when loading the page

GraphDB 8.4

Released: 30 November 2017

Component versions

RDF4J Connectors
2.2.2 7.2.0

Important

  • Fast loading mechanism without speed degradation for huge datasets - Preload tool
  • Minimal write performance overhead of the cluster compared to a single worker
  • Connectors can access and authenticate to secured ElasticSearch or SOLR endpoints
  • All database read queries and write updates operations are visible in Monitoring > Queries and Updates
  • Workbench supports overriding the default values of the sameAs result expansion, included inference results and result count behavior per user
  • Bug fixes and improvements in the initialization of new masters into the cluster

GraphDB Engine

Features and improvements

  • GDB-1861 - As an end-user I need to bulk load datasets over 10B without inference and plugins
  • GDB-2090 - As an user I need to use standard math functions with SPARQL
  • GDB-2131 - Improve default log message configuration

Bug fixes

  • GDB-1856 - GraphDB does not stop when shut down during import
  • GDB-2049 - Query text shouldn’t be printed in master’s enterprise log
  • GDB-2078 - Importing over 300 files one by one with parallel loader through Workbench fails with: java.IO.Exception: Too many open files
  • GDB-2079 - Limit the maximum entity-index-size parameter value according to the max integer
  • GDB-2098 - The beginning of the query is cut off the Query monitoring
  • GDB-2127 - Inferred statements are placed on a graph
  • GDB-2132 - Timeouts or errors on federated queries with multiple bindings may lead to hanging threads
  • GDB-2133 - Queries ran through the local API don’t return an error when a query is aborted
  • GDB-2135 - SPARQL comments make query evaluation fail
  • GDB-2164 - GraphDB fails to rebuild entity pool with out of memory error
  • GDB-2173 - There is no way to iterate over statements in a separate thread in a plugin
  • GDB-2191 - Special case with BIND clauses within a GRAPH clause with OPTIONALs cannot be handled by the query optimizer
  • GDB-2198 - Consistency checking does not work if data is imported via parallel load
  • GDB-2202 - PluginManager tries to interpret a statement pattern when shutdown has been called

GraphDB Cluster

Features and improvements

  • GDB-1765 - As an end-user I need a cluster which supports parallel inference

Bug fixes

  • GDB-1605 - Stopping the master, clearing the transaction log and a restart leads to a cluster which is out of sync
  • GDB-1917 - Read-only master cannot initialize worker
  • GDB-2040 - Cluster does not recover properly when 2 workers are removed and re-added while there are writes executing against the cluster
  • GDB-2061 - Cluster: 2M3W-1-RO-shared workers - the read-only master sees busy workers as OFF
  • GDB-2142 - Cluster should not retry query execution when the query ended with QueryInterruptedException
  • GDB-2153 - GraphDB EE read-only master doesn’t change the status of workers after a successful restoreFromImage
  • GDB-2155 - Query monitoring may cause OOM exception in a cluster without load
  • GDB-2194 - When one of the workers is OFF, JMX status is AVAILABLE
  • GDB-2268 - Worker goes out of sync if it’s shut down while executing a transaction

GraphDB Workbench

Features and improvements

  • GDB-2086 - As a user I want to be able to pin and unpin nodes in Visual graph
  • GDB-2139 - As a user I want to manage default settings for sameAs, inference and count in the SPARQL editor
  • GDB-2185 - As an administrator I need operation monitoring that supports updates to the existing query monitoring

Bug fixes

  • GDB-1898 - Graphs view triggers four getContext() queries in query monitoring
  • GDB-1982 - “Save” button appears in YASR Table tab after executing an update or ask query and then executing a select or a construct
  • GDB-2036 - “X running queries” is not clickable on Mozilla
  • GDB-2075 - Workbench fails to display an error message (but freezes) in the event of server file import failure
  • GDB-2081 - When importing many files in Workbench some of them remain in pending state even though they are imported
  • GDB-2099 - Namespaces: Prefix does not trim illegal characters upon edit
  • GDB-2105 - GraphDB Workbench loses all queries in the SPARQL view on page refresh with CTRL+SHIFT+R shortcut in FireFox
  • GDB-2107 - Binding validation of visual graph node basics query is too restrictive
  • GDB-2113 - Updating autocomplete configuration while running an update doesn’t update the list of labels
  • GDB-2138 - OntoRefine throws exceptions when splitting columns
  • GDB-2165 - Workbench API allows file imports with no write access via the import controller
  • GDB-2175 - Free access users should not be able to update saved SPARQL queries
  • GDB-2200 - The running queries/updates notification does not link properly for FIREFOX
  • GDB-2205 - No error message when create/update user with no read permissions to a repo

GraphDB Connectors & Plugins

Features and improvements

  • GDB-1940 - As an administrator I need to secure my ES/SOLR instance accessed by the connectors

Bug fixes

  • GDB-2034 - Autocomplete: The autocomplete fails to finish highlighting a resource when there are a couple of adjacent capital letters
  • GDB-2136 - Faults plugin doesn’t support timeout or query abort
  • GDB-2152 - Dropping connector instance can occur without active client
  • GDB-2171 - Documents added by user throw an NPE if they don’t have the right field _graphdb_id

GraphDB Distribution

Features and improvements

  • GDB-2141 - As an user I need basic authentication support with GraphDB puppet distribution for secured GraphDB downloads