GraphDB-Enterprise Release Notes

compared with
Current by Nikola Petrov
on Apr 09, 2015 17:47.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (6)

View Page History

{toc}

h1. GraphDB 6.1-SP3
This Service Pack 3 build addresses some reported problems with 6.1

h2. GraphDB Engine 6.1-b4371143

* OWLIM-1888 Better inference performance for datasets with big number of classes and onProperty restrictions
* Fixed a problem where queries containing UNION and BIND were under certain circumstances returning incorrect results
* New merge command for the storage tool
* OWLIM-1932 Count from graph http://www.ontotext.com/count does not work for describe queries
* OWLIM-1934 Removed some old and unwanted namespaces that were included by default
* OWLIM-1928 Added reversed numeric and date literal indices for better performance
* OWLIM-1990 Worker data is deleted when a plugin fails to initialize
* Using store-backed queue to keep transaction operations on the master - this should prevent out of memory errors when importing huge files


h2. GraphDB Workbench 6.4.1
- See all the release notes here: [https://confluence.ontotext.com/display/GraphDB6/GraphDB-Workbench+Release+Notes]


h2. GraphDB Connectors 3.1.4
- See all the release notes here: [https://confluence.ontotext.com/display/GraphDB6/GraphDB+Connectors+Release+notes]


h1. GraphDB 6.1-SP1
This Service Pack 1 build addresses consistency issue with the GraphDB Storage. The cluster's backup/restore functionality is also fixed.

h2. GraphDB 6.1.8410
- extended new cluster backup/restore to support multiple named backups. Important note: the backup now uses a name instead of an absolute folder
- fixes for the master URL parameter (autodetected in most cases, thus no need to specify manually)
- minor cluster improvements (shutdown on OOM during sync; worker: handling multiple initializations and no reporting of missing fingerprints on init; fixed race condition in replication; new internal URIs (not URLs) for replication)
- fixed: [owlim-1853] LoadRDF under Windows sometimes does not include statements in the PSO index and the indexes are incosistent;
- Added a check/warning to see if there is enough memory for the entity pool when it gets restored from persistence (-Xmx - cache-memory should be >= entity pool size * 1.25, i.e. 25% overhead is left for the datatype index and other in-memory structures included in the entity pool and for other purposes, e.g. for running queries)
- Constraint validation and support for multiple rulesets is out of its experimental stage and now in production. See the docs here: [https://confluence.ontotext.com/display/GraphDB6/GraphDB+Constraint+Validation]

h2. GraphDB Workbench 6.3.2
- See all the release notes here: [https://confluence.ontotext.com/display/GraphDB6/GraphDB-Workbench+Release+Notes]


h1. GraphDB - 6.1.8316
This is an Enterprise release only.
- dedicated peer dispatch threads
- fixed split-brain recovery
- retry serving replication data on failure
- exposed exceptions thrown from replication server
- Client API: Changed the master retry policy (do not check every master too often; but still make sure that when previously unavailable master becomes available we detect that)

- cleanup target directory on accepting replication data
- 60s timeout in replication client
- limited retries in the replication server
- replication client startup delay patch
- retry serving replication data on failure
- exposed exceptions thrown from the replication server

h2. Other improvements:
- [OWLIM-1838] Custom NTriples/NQuads parser: ArrayOutOfBoundsException can be thrown on empty lines while parsing and then NPE while trying to process t.getMessage() which may be null
- [OWLIM-1834] Fixed: LoadRDF Tool doesn't work with GraphDB Enterprise
- [W-44] Introduced a parameter 'in-clause-max-members' (defaults to 16) which limits the number of entities specified in the IN clause. If the IN clause contains more elements then it doesn't get optimized. won't be optimized to a UNION query
- [W-55] Fixed the ASC/DESC issue in ORDER BY clause when the variable in the ORDER BY is in an OPTIONAL clause (the issue was different number of results returned in ASC/DESC cases).