GraphKnowledge

graph-studio

Graph Lakehouse DB 3.0 Releases

Please be advised that all Altair Graph Lakehouse 3.0 versions are officially deprecated as of March 24th, 2026. These versions will continue to be supported with critical security patches for a six-month transition period, reaching full End-of-Life (EOL) on September 24th, 2026. After this date, 3.0 versions will no longer receive updates, and technical support will be discontinued.

To view the release notes for an Graph Lakehouse DB 3.0 release, select the version from the list below. The release notes for each version describe the product changes from the previous version.

Graph Lakehouse DB Version 3.0.0

This section describes the new features, improvements, and fixes in Graph Lakehouse DB Version 3.0.0.

New Features and Improvements

Fixes

Compatibility with RHEL/Rocky 9 Operating Systems

Version 3.0.0 is compatible with RHEL/Rocky 9 operating systems and is not supported on RHEL/CentOS 7 or 8.

Added Support for Data Validation with SHACL

Version 3.0.0 adds support for using the W3C standard Shapes Constraint Language (SHACL) to validate graph data. For more information, including the list of constraints that are supported, see Validate Data with SHACL (Preview) in the Graph Lakehouse documentation.

Added a Weighted PageRank Graph Algorithm

Version 3.0.0 adds a PageRank graph algorithm that accepts a weighted property as input.

Added Support for GraalVM 17

Version 3.0.0 adds support for using GraalVM as the Java Virtual Environment. You have the option to use OpenJDK 17 or GraalVM 17.

Added the Option to Vacuum the URI Dictionary

The database vacuum process runs automatically to improve data organization in memory, deduplicate data, and reclaim memory after data is deleted. Previously this process could only operate on the graphs in the database but not the URI dictionary, which can consume a significant amount of memory. In Version 3.0.0, the vacuum process can now be run against the URI dictionary to remove unused URIs and reclaim unused memory. To enable the option to vacuum the dictionary, the enable_vacuum_uri setting must be set to true in the server settings file. For information about changing settings, see Change System Settings in the Graph Lakehouse documentation.

Initiating the URI dictionary vacuum process should only be done during a maintenance window when no one else is actively using Graph Lakehouse. To start the vacuum process, run the following SPARQL query:

VACUUM URI

Added Support for Loading Labeled Property Graph (RDF*) Files with the IO Load Service

Version 3.0.0 updates the IO Load Service to add support for loading files that include relationship properties. For information about loading data with the IO Load Service, see Load RDF Files with the IO Load Service in the Graph Lakehouse documentation.

Added a System Table to Log Compilation Errors

Version 3.0.0 introduces the sth_failed_compile system table, which captures query compilation errors. Previously this information was captured only in the compile-errors.log file.

Added a Memory Allocation System Table

Version 3.0.0 introduces the stc_tcmalloc_state system table, which logs memory allocation information and can be used to discern between the memory usage as reported by the operating system versus the memory that Graph Lakehouse is actually using. For example, suppose that the database uses 100GB of data at rest and then uses another 100GB of memory while running queries, for a total of 200GB while queries are running. Once the queries finish, Graph Lakehouse should again use only 100GB of memory. However, the OS may report that 200GB of memory is still in use by Graph Lakehouse because Graph Lakehouse does not always return memory to the OS; it may retain the unused memory for future use. In the stc_tcmalloc_state table, the current_allocated_bytes column contains the Graph Lakehouse-reported value and heap_size contains the OS-reported value.

Upgraded the Version of gRPC

Version 3.0.0 upgrades the gRPC version to 1.48.0.

Updated the Apache Arrow Extensions to Apache Arrow 11

Version 3.0.0 upgrades the Apache Arrow C++ extensions to Apache Arrow version 11.

Enhanced the GDI to Capture Property Keys from JSON Files

Version 3.0.0 updates the GDI to add the ability to capture the names of property keys in JSON files. In GDI Generator queries, this type of metadata can be selected from JSON files by including a variable as the s:selector and using the same variable as the s:key. For more information, see Capturing Property Keys.

Improved Query Cancellation Responsiveness

Version 3.0.0 includes an enhancement that decreases the time it takes to cancel most queries.

Improved Logging for the JVM Subsystem

Version 3.0.0 improves logging for the JVM subsystem to help diagnose the cause of issues that result from queries that run Java extensions.

Removed Duplicate Self-Signed Certificates and Key Files

Version 3.0.0 removes the certificate and public and private key files from the anzograph/etc directory. Now, the etc directory only includes symbolic links to the certificate and key files in the anzograph/config directory. This change makes it easier to replace the self-signed files with custom files because you do not need to remove the files from etc. For information about replacing the default files, see Replace the Default Self-Signed Certificates with Trusted Certificates.

UPPER and LOWER Functions did not Convert Strings with Umlaut Letters

Version 3.0.0 corrects an issue that prevented the UPPER and LOWER functions from converting strings to upper or lower case if the strings included umlauts.

Inconsistent Query Performance Based on Memory Usage

Version 3.0.0 corrects an issue that could cause the memory allocator to become a query performance bottleneck when memory usage was near the maximum limit.

Binding Error for GDI ElasticSource Query with Aggregations

Version 3.0.0 resolves an issue that caused a "Could not determine binding context from binding" error to be returned when a user ran a GDI Elasticsearch query that included es:aggregations options.

Source: https://docs.sw.siemens.com/documentation/external/PL20260212925461721/en-US/graph_studio/relnotes/v30-releases.htm · retrieved 2026-08-23