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

Released: 09 October 2017

Component versions

RDF4J Connectors
2.2.2 7.1.0

Important

  • Fixed major problem with query monitoring and improved cluster stability
  • Fixed important issues in GraphDB Engine
  • Fixed a problem with importing many files in Workbench
  • Added some visual graph usability improvements
  • Fixed several minor bugs in Workbench

GraphDB Engine

Bug fixes

  • GDB-2127 - Inferred statements are placed in 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

GraphDB Workbench

Features and improvements

  • GDB-2086 - Visual graph usability improvements - pinning and unpinning nodes

Bug fixes

  • GDB-2081 - Importing many files process can hang
  • GDB-2099 - Namespaces: Prefix does not trim illegal characters upon edit
  • GDB-2107 - Binding validation of visual graph node basics query is too restrictive
  • GDB-2138 - OntoRefine throws exceptions when splitting columns

GraphDB Cluster

Bug fixes

  • GDB-2142 - Cluster should not retry query execution when the query ended with QueryInterruptedException
  • GDB-2098 - The beginning of the query is cut off the Query monitoring
  • GDB-2155 - Query monitoring may cause OOM exception in a cluster without load

GraphDB Connectors and Plugins

Bug fixes

  • GDB-2136 - Faults plugin doesn’t support timeout or query abort

GraphDB Distribution

  • GDB-2159 - dev-examples should not be packaged as jar and included in the lib directory of the distribution

GraphDB 8.3

Released: 31 August 2017

Component versions

RDF4J Connectors
2.2.2 7.1.0

Important

  • Workers serving replication or backup remain in a read-only state. The cluster can automatically self-recover without losing any reads even if there is a single operation worker.
  • Master node can monitor and stop queries running on the workers.
  • Simplified table to RDF transformation in OntoRefine assisted with a code generation, which substantially reduces the time generate RDF data.
  • Fully customizable graph views with SPARQL queries. A wizard like interface guides the user how to create various visualisations.
  • A progress bar indicates the remaining time to build a Connector index.
  • Upgrade to the latest RDF4J public release. The full list of bugfixes is available at https://github.com/eclipse/rdf4j/milestone/21?closed=1

GraphDB Engine

Features and improvements

  • GDB-1220 - The TriplePattern iterator should use FROM / FROM NAMED graphs as bindings when the context index is switched on rather than using them as filters
  • GDB-1862 - Upgrade to latest RDF4J 2.2.x
  • GDB-1889 - Added statistics to monitor the loading process during file loads

Bug fixes

  • GDB-1710 - Literal index may fail to start after abnormal process termination
  • GDB-1865 - Prevent the import of RDF files from Workbench through worker in a cluster
  • GDB-1888 - SPARQL queries with SERVICE and BIND operators may return a serialization error
  • GDB-1890 - After deleting an owl:sameAs, the following addition to the statement fails to infer the same data
  • GDB-1958 - Reinfer does not remove the inference closure
  • GDB-2073 - Federated queries with join to a subselect aren’t handled the same way as other federated queries regarding query monitoring/query abort

GraphDB Workbench

Features and improvements

  • GDB-1414 - As an end-user I want simpler interface for RDF-ing data with OntoRefine, so it can show me how to start
  • GDB-1829 - As a user I want to create custom visualisations by configuring Visual Graph view with SPARQL queries
  • GDB-1915 - Unified look and feel of OntoRefine SPARQL with main SPARQL editor
  • GDB-1979 - Improved behaviour and user feedback when a big saved results in the SPARQL view make things very sluggish
  • GDB-1996 - Add progress monitoring for connector management
  • GDB-2000 - Simplify the connector management view to show all connectors at once (no tabs)

Bug fixes

  • GDB-1591 - OntoRefine: The query limit is not respected
  • GDB-1592 - OntoRefine: cannot upload a file from a Web Address or Clipboard
  • GDB-1912 - Reinitialise the object information in the Workbench’s internal database if the application hits a deserialization error
  • GDB-1932 - Switching repositories in the SPARQL view adds extra tabs to the results (Table, Raw, Google Chart, etc)
  • GDB-1934 - Unnecessary extra space between the SPARQL results table and the status bar/search filter in SPARQL view
  • GDB-1936 - Prefixes not added on paste in the SPARQL view
  • GDB-1955 - OntoRefine: Count limit does not work for Facets
  • GDB-1956 - OntoRefine: JSONException is thrown when saving a Numeric Facet with an empty value
  • GDB-1965 - Visual graph: URL encoded resource links are truncated at the special character
  • GDB-1987 - Cannot set the repository title/description to the empty string
  • GDB-1992 - When free access is enabled but no repositories are selected for it the status bar shows “No repositories” out of place
  • GDB-2004 - Editing the credentials of a remote location doesn’t work (leads to errors in the log)
  • GDB-2007 - When autocomplete is ON it’s not possible to use an IRI in the search form that autocomplete doesn’t know about
  • GDB-2028 - Problem importing many files in the workbench
  • GDB-2037 - SPARQL view: tabs created or deleted from another browser window may result in view with unselected tab
  • GDB-2047 - Workbench CSS has unnecessary padding/margin at bottom, which creates scrollbars
  • GDB-2076 - Visual graph: consistent handling of foaf/dbpedia predicates that point to IRIs but are treated as literals

GraphDB Cluster

Features and improvements

  • GDB-1749 - As a cluster administrator I want readable worker while they are serving a replication or a backup
  • GDB-1766 - As an administrator I need to profile and stop all current cluster queries from the master
  • GDB-1864 - Improve logging when cluster worker is unable to make a backup

Bug fixes

  • GDB-1667 - Multimaster cluster generates “Not in GZIP format” error on Windows
  • GDB-2054 - Local consistency header not processed when Workbench is active
  • GDB-2100 - Cluster fails to recover after a restore operation and reports some of the workers in ouf of sync forced state

GraphDB Connectors

Features and improvements

  • GDB-1943 - Implement nested object support for geo_point in the Elasticsearch connector
  • GDB-1981 - Upgrade Lucene/Solr/Elasticsearch to 6.6.0/6.6.0/5.5.0
  • GDB-1996 - Add progress monitoring for connector management

Bug fixes

  • GDB-1850 - Connectors may fail to init when a given connector instance is inaccessible
  • GDB-1923 - Nested objects in the Elasticsearch connector don’t work with literals
  • GDB-1927 - Elasticsearch nested objects of type “nested” are indexed as “object”