Introduction
See the general release-notes document for links to release notes for other recent releases and the current release.
This document contains all changes in version 8.1.1 as well as changes in release 8.1.0 (releases where the change is in the third place contain either bug fixes or improvements to an existing feature; there are no significant new features.)
Change History repeats the list of user-visible modifications for this release and includes similar lists for all earlier releases.
Release 8.1.1
This is a maintenance release, with SPARQL fixes, changes to the New WebView interface, and improved documentation.
Release 8.1.0
This release contains fixes and enhancements as described below. There are no programmer or admin notes.
New in Release 8.1.0
Release 8.1.0 is a major release with important new features.
- Enhanced support for vector databases
Database internal format is unchanged from version the previous version (8.0.x)
Release 6.4.6 had a different internal format. All releases since then have the same internal format. This means version 6.5.0 through 7.3.1 repositories can be directly loaded into version 8.1.0 without upgrading. Note that backing up repositories before loading them into a new version is always recommended. Once a database has been used in a later release, it cannot be used in an earlier release regardless of whether or not the database format is the same. Upgrading is discussed in the Repository Upgrading document.
Version 8.1.1 Admin notes
There are no additional admin motes for release 8.1.1.
Version 8.1.0 Admin notes
These three items were actually introduced in version 8.0.0 but the changes are important enough to repeat.
This sections notes changes which may affect AllegroGraph administration, which includes managing users, dealing with passwords, and so on.
The agtool program, included with the AllegroGraph distribution, is also available as a separate download and can be run on any x86-64 Linux machine (same download location as the AllegroGraph downloads). If you want to have agtool available on machines other than the one where AllegroGraph is installed, use the separately downloaded version as it comes with all necessary additional files needed to run agtool. See agtool for installation instructions.
Support for specifying which users (and roles) can view which triples. AllegroGraph has for some time allowed using attributes to restrict access to triples by selected users, but this required SPARQL queries to be processed using a preprocessor which added the correct prefix to queries. These prefixes specified user attribute values. Users themselves could not directly query the AllegroGraph server as that would allow them to bypass restrictions. In 8.0.0, control has been moved within the AllegroGraph server and users can be assigned attribute values which, combined with triple attribute values, will determine whether the user can or cannot access specific triples.
There is a new version of AGWebView. As with traditional WebView adminstration can be managed using the new version. Both the new and traditional versions are supported.
Version 8.1.1 Programmer notes
There are no programmer nore for release 8.1.1.
Version 8.1.0 Programmer notes
- The contents of the .def file needed for the LLM Retrieval Augmented Generation (RAG) example have changed. See the RAG example for details.
Version 8.0.0 Programmer notes
Because these version 8.0.0 changes were significant, we repeat the programmer notes in these version 8.1.x programmer notes.
This section notes changes which may affect how certain code or operations work compared to earlier releases. These are emphasized here because the changes may be unexpected. The complete list of user-visible changes below also mentions these changes in a shorter format.
The tutorials/ subdirectory moved (repeat from v8.0.0 release notes) to github tutorials location in the Franzinc agraph-example github repository. This directory used to be included in the distribution. We moved it so that it is accessible to users without access to distribution files and also so tutorial examples can be improved (or fixed) more easily.
New AGWebView implementation. (repeat from v8.0.0 release notes) There is a new implementation of AGWebView. The old implementation is still supported and indeed is what comes up when you initiate AGWebView. The new implementation is described in the New ACWebView document.
User-visible changes version 8.1.1
AllegroGraph Server: General Changes
No significant changes.
HTTP Client
No significant changes.
SPARQL
AG-643 - incorrect results when using complex FILTER [NOT] EXIST clauses
Due to a regression introduced in AllegroGraph v8.0.0, queries with complex FILTER [NOT] EXISTS clauses (e.g. with inlined VALUES and inner FILTER) could potentially produce fewer results because of a join operation misconfiguration. This has been fixed.
AG-737 - SPARQL parser fails on space-separated + property path modifiers
AllegroGraph's SPARQL parser used to try to interpret + character after the predicate part of a triple pattern as an explicit numeric sign of the object part if it was separated from the predicate by a space:
?s :p + ?o -> ?s :p (+ ?o)
?s :p +?o -> ?s :p (+ ?o)
?s :p+ ?o -> ?s (:p +) ?o This has been fixed and now the correct grouping is used:
?s :p + ?o -> ?s (:p +) ?o
?s :p +?o -> ?s :p (+ ?o)
?s :p+ ?o -> ?s (:p +) ?o The + character is grouped with the object part of the pattern as its explicit numeric sign only if there is no space between it and the object, and as a path modifier in all other cases.
AG-770 - inconsistent results of joins with UNION on SBQE
SPARQL queries with UNION operations could lose some of the results on SBQE if the operands had differing sets of bound variables, because the result of the UNION would incorrectly inherit bound variables of its left-hand side operand. For example the result of the following operation
{ VALUES ?s { :person1 :person2 } }
UNION
{ VALUES ?o { :person1 :person2 :person3 } } would have ?s marked as bound, while it is only bound in 2 out of 5 results, causing a subsequent join operation to lose results. This has been fixed by correctly computing the set of bound variables for the result of the UNION.
AGWebView
AG-354 - Fix losing content of query tabs in New WebView after reload
Before 8.1.1, in New WebView unsaved changes in queries were lost after page reload, page closing, and user logout (explicit or implicit due to inactivity). Now, in New WebView all query changes persist on the server side per user for a repository. In other words, even unsaved queries are saved automatically. The difference between saved and unsaved queries is the following:
- Unsaved queries don't have persistent names.
- Unsaved queries aren't listed in the right sidebar in the "Saved queries" group, only in the query tab.
- Unsaved queries have user scope. Saved queries can be saved per repo, e.g. any user with read access could see them.
- Natural language queries were saved in browser's local storage which is limited to 5MB only. Now, New WebView stores results on the server side which is limited only by server's storage.
AG-367 - Make the query language option local to a query tab instead of being global for a user
Before 8.1.1, the query language was part of "In-Browser query option" group and global for a user. Now, New WebView has language attribute for each query (saved or unsaved). The language is displayed as an icon in the query tab. Additionally, rename the "Free text" to "Text Search", and "Query documents" to "ChatStream - Natural Language" queries.
Changes to the Lisp API
No significant changes.
Prolog
No significant changes.
Documentation
No significant changes.
Distributed AllegroGraph
No significant changes.
User-visible changes version 8.1.0
AllegroGraph Server: General Changes
No significant changes.
HTTP Client
No significant changes.
SPARQL
No significant changes.
AGWebView
No significant changes.
Changes to the Lisp API
No significant changes.
Prolog
No significant changes.
Documentation
No significant changes.
Distributed AllegroGraph
No significant changes.
User-visible changes in earlier releases and the current release
See the general release-notes document for links to release notes for other recent releases and the current release. See Change History for user-visible changes to all earlier releases.