Table of Contents

Version 3 History

Changes from 3.1.1 to 3.2

General

Server

Lisp

SPARQL

Java

Other

Changes from 3.1 to 3.1.1

Changes from 3.0.1 to 3.1

API Changes

New Features and improvements

Bug Fixes

SPARQL

Java

Changes from 3.0 to 3.0.1

New Features and improvements

AllegroGraphService

Lisp Bug fixes and Enhancements

Java

SPARQL

General

Changes from 2.2.5 to 3.0

Major New Features

New Features and Improvements

Incompatible Changes

Java API Changes

Version 2 History

Changes from 2.2.4 to 2.2.5

SPARQL

Lisp

Java

Changes from 2.2.3 to 2.2.4

Enhancements

Bug Fixes

Changes from 2.2.2 to 2.2.3

Bug Fixes

Changes from 2.2.1 to 2.2.2

Enhancements

Bug fixes

Changes from 2.2 to 2.2.1

Enhancements

Bug fixes

Changes from 2.1 to 2.2

Major Changes

Changes from 2.0.1 to 2.1

General

Java-specific

Changes from 2.0 to 2.0.1

New functionality

SPARQL / twinql improvements

Fixes

Removed or deprecated functionality

Known problems

Java Specific Changes

Changes from 1.2.6 to 2.0

Major improvements and changes

Miscellaneous changes

API improvements and additions

Java related

Version 1.0 History

Changes from 1.2.5 to 1.2.6

Changes from 1.2.4 to 1.2.5

Changes from 1.2.3 to 1.2.4

Changes from 1.2.2 to 1.2.3

Changes from 1.2.1 to 1.2.2

Changes from 1.2.0 to 1.2.1

Changes from 1.1 to 1.2

Major changes and enhancements

Minor changes and enhancements

Changes from 1.0 to 1.1

Major changes

Minor changes

Minor Enhancements ¯

Changes in the Java Interface

Version 3 History

Changes from 3.1.1 to 3.2

General

AllegroGraph 3.2 introduces a new query planner to the Prolog select family of macros. This planner performs both clause re-ordering and re-writing to make select queries much more efficient. The underlying query engine also now creates temporary maps for particular subsets of the triples in a store. These maps make many queries significantly faster.

We have increased the maximum size of the string-dictionary to 8-GB. Existing triple-stores will need to be converted to use the new format and new stores will not be readable by previous versions of AllegroGraph. If a store is opened in Lisp, then a restart will be offered to convert the store. Otherwise, the convertdb command-line tool should be used.

In addition, The internal encoding of Cartesian geospatial subtypes has changed. Triple-stores containing Cartesian geospatial data created with earlier releases can not be opened under under 3.2 and must be re-built. Contact us if this is a serious problem. Note that spherical data is unaffected.

Finally, AllegroGraph no longer modifies the Lisp readtable (with the enable-!-reader function). If your code relies on the reader, then you will either need to enable it yourself or use the facilities of Allegro's named readtables).

Server

Lisp

Enhancements and Features
Fixed bugs and other corrections

SPARQL

The :algebra query engine is now used for all queries unless a different query engine is explicitly chosen. It is also the main focus of future AllegroGraph development. Any bugs (such as extraordinary differences in behavior between the :algebra and the :allegrograph-2 engines) should be addressed to allegrograph-support@franz.com.

Enhancements
Bug fixes

Java

Major Java API changes:

Other

Changes from 3.1 to 3.1.1

The additions since version 3.1 were for the Python client API. The documents of interest for Python users are the Python Tutorial and the Installation notes for the Python client.

Changes from 3.0.1 to 3.1

API Changes

New Features and improvements

Bug Fixes

SPARQL

Java

The Java API in AG 3.1 has been re-organized internally but there are few user-visible changes. Existing applications will run without change.

The current API will be deprecated in the next release, when the new API is exposed as the native API to AG.

We have added extensions that enable access to AG with Jena and Sesame 2.x API calls. Applications using Jena or Sesame 2.x must use the new revised API to access native AG features. Note that we are continuing to tune and improve both of these APIs and will release updates on a regular basis. Be sure to consult Franz's webpage detailing recent AllegroGraph patches and updates for more information.

Details:

Changes from 3.0 to 3.0.1

New Features and improvements

AllegroGraphService

Lisp Bug fixes and Enhancements

Java

The AllegroGraph Java API up to this release has included the openrdf.org.model interfaces from Sesame 1.2. These interfaces will not be implemented or included in the API after this release. We plan to provide Sesame 2.0 compatibility in the next release of AllegroGraph.

Java API changes in 3.0.1:

SPARQL

General

Changes from 2.2.5 to 3.0

Major New Features

New Features and Improvements

SPARQL updates

Incompatible Changes

Java API Changes

New classes:

This new behavior is similar but not identical to earlier namespace behavior.

There is no Java access to the global namespace definitions in Lisp. The global namespace definitions in Lisp have no effect on the Java client interface.

NEW Methods in class AllegroGraph:
NEW Methods in Class AllegroGraphConnection
Bug Fixes (partial list):

Version 2 History

Changes from 2.2.4 to 2.2.5

SPARQL

Lisp

Java

Changes from 2.2.3 to 2.2.4

Enhancements

SPARQL / twinql
Lisp / AllegroGraph Core

Bug Fixes

Java
SPARQL / twinql

Changes from 2.2.2 to 2.2.3

Bug Fixes

Changes from 2.2.1 to 2.2.2

Enhancements

Bug fixes

Changes from 2.2 to 2.2.1

Enhancements

Bug fixes

Changes from 2.1 to 2.2

Major Changes

Lisp
New Features
New functions
API Changes and Improvements

Bug fixes

SPARQL
RDFS++ Reasoner
Java

Changes from 2.0.1 to 2.1

General

We have improved AllegroGraph's string dictionary usage and the speed of its internal hashing Algorithms. These improve performance on all platforms but allow for dramatic speed increases under 32-bit Windows. Unfortunately, these changes mean that triple-stores built with previous versions of AllegroGraph will no longer operate with AllegroGraph 2.1. If you have triple-stores that you would like to migrate from an earlier version to version 2.1 (rather than rebuilding your stores from your original data), you will need to export your data and import it into the new format. If you find yourself in this situation, please contact support@franz for assistance before you begin the process.

Performance improvements
Bug fixes

Java-specific

Major Changes
Minor Changes
Bug fixes

Changes from 2.0 to 2.0.1

New functionality

SPARQL / twinql improvements

Fixes

Removed or deprecated functionality

Known problems

Java Specific Changes

New functions and improvements
Fixes

Changes from 1.2.6 to 2.0

Major improvements and changes

Miscellaneous changes

API improvements and additions

Java related

The AllegroGraph Java API in Version 2.0 is similar to the API in Version 1.2, but many method signatures have changed because the implementation of the triple store has been revised extensively. All 1.2 application programs need to be inspected carefully and revised accordingly.

Major change summary:

Version 1.0 History

Changes from 1.2.5 to 1.2.6

Changes from 1.2.4 to 1.2.5

Changes from 1.2.3 to 1.2.4

Changes from 1.2.2 to 1.2.3

Changes to the Java interface:

Changes from 1.2.1 to 1.2.2

Changes to the Java interface:

Changes from 1.2.0 to 1.2.1

Changes to the Java interface:

Changes from 1.1 to 1.2

Major changes and enhancements

AllegroGraph is now integrated with TopBraidComposer and can run as a service accessible to Java programmers using either JLinker or a direct socket interface.

AllegroGraph now comes with a full SPARQL implementation via its twinql sub-system. See the AllegroGraph SPARQL tutorial, the twinql API reference manual, and the release notes for more details.

Minor changes and enhancements

Changes from 1.0 to 1.1

Major changes

We are now using a faster mechanism to store and retrieve URI information. The new method also uses much less memory so that larger RDF files can be loaded.

The triple store disk format has changed between release 1.0 and release 1.1. Release 1.1 will not read 1.0 triple stores. The easiest thing to do is to recreate your databases with the new version. Please contact us (support@franz.com) if you need assistance in converting your 1.0 triple stores into the new format. The section on "Savings Triples to a file" below may also be helpful.

Minor changes

Minor Enhancements ¯

Changes in the Java Interface