Graph Lakehouse 2025.0 Database 3.2 Releases

To view the release notes for a Graph Lakehouse database 3.2 release, select the version from the list below. The release notes for each version describe the product changes from the previous version.

Graph Lakehouse Database Version 3.2.2

This section describes the fixes and improvements in Graph Lakehouse database v3.2.2.

This version includes patches for identified security vulnerabilities. For details about the patches, see Patched Vulnerabilities in the Graph Studio Release Notes.

New Features and Improvements

Fixes

GDI Support for Inline View Definitions

Version 3.2.2 adds GDI support for inline view definitions to enable the parsing of queries with inline views on the View step that are now supported by the Graph Studio SPARQL parser.

Improved Handling of the UStar Format when Loading X-Rays

Version 3.2.2 improves the handling of the UStar format by Graph Studio when trying to load X-Rays using UDS Remote IO service.

Updates to FIPS Compliance

Load Query Error on FIPS-enabled Nodes

Version 3.2.2 resolves an issue where a load query execution in the User-Defined Services extension library fails on a FIPS-enabled nodes with the error 'Crypto error while init Md5Hash.'

Webdav Write Queries Fail on FIPS-enabled Nodes with Internal Server Error(500)

Version 3.2.2 fixes an issue where a webdav write query execution in the User-Defined Services extension library fails on FIPS-enabled nodes, resulting in an 'Internal Server Error (500)' exception.

GDI Loads Non-FIPS Compliant JDBC Drivers in FIPS-Enabled Mode

Version 3.2.2 addresses an issue in GDI where a non-FIPS compliant JDBC driver (Snowflake) could be loaded via available Database Connections in the Admin UI even when the FIPS mode is enabled across the Graph Lakehouse cluster.

Deploying Graph Lakehouse Operator and CR with Managed Altair Units Licensing Causes DB Pod to Restart

Version 3.2.2 fixes an issue where the DB pod unnecessarily restarts upon deploying Graph Lakehouse operator (anzograph-operator) with Managed Altair Units Licensing using Altair One credentials. Operator logs contain database deployment and reconciler errors 'Operation cannot be fulfilled on statefulsets.apps \"anzograph-pf1-db\": the object has been modified; please apply your changes to the latest version and try again'

Error Loading an X-Ray Captured through Graph Studio UI

Version 3.2.2 resolves an issue where loading an X-Ray captured from Graph Studio UI causes an error. When the query is loaded with UDS Remote IO service using the query ./azgi -timer -wide -c "prefix io: <http://cambridgesemantics.com/anzograph/io#> select (count (*) as ?count) where { service io:load('//opt/altair/anzograph/bin/filename.xray'){}. }", this results in an error "Exception thrown from within an extension - Unrecognized tar format".

Various Issues Preventing the Execution of a Serialized Plan

Version 3.2.2 fixes various issues preventing the execution of a serialized plan and handling plans with Append or Decompressor plan nodes.

Numeric Overflow When Calculating Date/Time Deltas for Values Far from the Epoch

Version 3.2.2 resolves a numeric overflow issue in GDI when calculating date/time deltas for values far from the epoch (e.g. 0215-03-18T00:00:00Z).

Graph Lakehouse Database Version 3.2.1

This section describes the fixes and improvements in Graph Lakehouse database v3.2.1.

This version includes patches for identified security vulnerabilities. For details about the patches, see Patched Vulnerabilities in the Graph Studio Release Notes.

New Features and Improvements

Fixes

FIPS Compliance

Version 3.2.1 is compliant with FIPS crypto policies regulations.

Support for "select * {}" Statement

Version 3.2.1 adds support for the SPARQL statement select * {}, which is valid per the SPARQL 1.1 specification and returns the same result as Apache Jena if the enable_unbound_variables configuration setting is set to true.

Unencoded Data Binding Selectors Generated in GDI Cause Missing Data for Imported File

Version 3.2.1 resolves an issue where GDI does not encode paths and selectors when generating data binding information to drive the source onboarding process. When path navigation elements that might appear in the field names are not escaped properly, this causes data to be missing when viewing or profiling data in imported files in the graphmart source layers.

Insufficient Diagnostic Information Captured when an OOM Event Occurs

Version 3.2.1 addresses an issue with insufficient diagnostics for the Out of Memory events caused by the system allocator TCMalloc running out of memory. Snapshots, logs, timestamps and other relevant attributes are now properly captured.

Error Loading AnzoGraph Data in a Graphmart: "Exceeds concurrent load limit 100"

Version 3.2.1 resolves an issue that occurs when loading ontologies for a layer in a Graphmart: "ErrorCode [10503] Error loading AnzoGraph data <Exception>: Exceeds concurrent load limit 100". The error is caused by leaking pload context resources that the database allocates when reading from multiple external files.

SPARQL Endpoint - Difference in Results Output Caused by Hidden Whitespace

Version 3.2.1 fixes an issue with querying the SPARQL endpoint on AnzoGraph DB, where the CSV results are prefixed with a hidden whitespace that was not there previously, which causes an error in the code running on Oracle RDS.

Failure to Load Xray Step: "Unable to open xray buffer"

Version 3.2.1 resolves an issue where adding a Load Xray Step and refreshing / reloading the Graphmart causes an exception within the io#load extension: "unable to open xray buffer, return error code(-30)"

Xray Does Not Capture All Diagnostic Information

Version 3.2.1 fixes an issue where some diagnostic information was not being captured when taking an Xray.

Graph Lakehouse Database Version 3.2.0

This section describes the new features, improvements and fixes in Graph Lakehouse database v3.2.0.

This version includes patches for identified security vulnerabilities. For details about the patches, see Patched Vulnerabilities in the Graph Studio Release Notes.

New Features and Improvements

Fixes

Altair Units Licensing

Version 3.2.0 introduces Altair Units Licensing - a value-based license management system enabling metered usage of Graph Lakehouse and all other Altair products. Graph Lakehouse belongs to the Altair Data Analytics suite of applications, all of which have the capability to use a single pool of recyclable Altair Units. The license units consumption of Graph Lakehouse depends on the CPU resources (the number of CPU cores) on the host system. As of this version, Graph Lakehouse consumes 6 units per core.

Note: Even though the slices_per_node setting is used by Graph Lakehouse for runtime behavior, it does not affect the license units draw, which depends only on the total number of CPU cores on the host hardware.

Cambridge Semantics license keys are still supported as a legacy licensing method to ease the transition to the new licensing system for existing customers.

Product Rebranding

For version 3.2.0, AnzoGraph has been rebranded to Altair® Graph Lakehouse™, and Anzo has been rebranded to Altair® Graph Studio™.

Database Crashes Due to Allocation Failure Using TCMalloc

Version 3.2.0 fixes an issue where running a query in AnzoGraph DB CLI multiple consecutive times, the database crashes with allocation failure in the TCMalloc memory allocator.

System Management Daemon Does Not Reserve Memory According To License Restrictions

Version 3.2.0 corrects an issue where the system management daemon, azgmgrd, does not reserve memory in accordance with the license restrictions.

AnzoGraph May Report Offline Status in Low-Memory Conditions

Version 3.2.0 resolves an issue where, in low memory conditions, azgctl -status may report that AnzoGraph is offline, whereas both the process and manager process are still running.

Error Message Not Provided with Error Code while Reading Xray tar File

Version 3.2.0 fixes an issue where the database only provides an error code without the associated error message when failing to load xray through the io#load service.