GraphDB-Enterprise Release Notes

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

Changes (5)

View Page History
- 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).