GraphDB 10.6: Enhanced Data Management Capabilities and Improved User Experience

The new release brings fine-grained access control, streamlined node addition in clusters and upgraded SPARQL GUI in the workbench.

New York, Sofia, Basel Wednesday, February 21, 2024

We are pleased to announce the release of GraphDB 10.6.

GraphDB 10.6 introduces a suite of enhancements aimed at refining its functionality and user experience. This update sees the expansion of the Fine-Grained Access Control system to cover a broader range of operations, ensuring more nuanced access control at multiple levels. Significant improvements in the integration of new nodes into GraphDB clusters, particularly in cloud environments, have been made to streamline operations and reduce downtime. 

The YASGUI component in the GraphDB Workbench SPARQL editor has been upgraded to address multiple bugs, and allow for concurrent running of multiple SPARQL queries and more efficient data handling. Additionally, there is a focus on keeping third-party libraries up-to-date, ensuring the security and reliability of the product. These developments collectively enhance GraphDB’s capabilities in managing complex data environments and improve the overall user experience.

Manage Access with Fine-Grained Access Control

GraphDB 10.6 introduces the Fine-Grained Access Control (FGAC) system. This extends the quad-based access control for statement read operations, introduced in GraphDB 10.4, to cover statement write operations and other operations not directly related to statements.

FGAC provides access control below the repository level and employs an Access Control List (ACL) consisting of a number of rules. Each rule has a policy (deny or allow), role membership, scope, operation type (read or write), and optional elements that depend on the scope and identify specific resources within a given scope. The first matching rule determines whether a given resource can be read or written to.

The rule scope is a new concept that determines the general applicability of a rule based on what components of the GraphDB engine are responsible for executing the operation.

The Statement scope governs operations that affect repository statements, including read and write access to all data statements. It is typically used for restricting access to specific predicates (for example, salary) or entire named graphs.

The Clear Graph scope controls operations that delete statements identified only by a named graph or all graphs at once, especially used for restricting access to the ‘CLEAR ALL’ operation.

The Plugin scope applies to operations managed by plugins and can be used to restrict write operations on GraphDB Connectors to prevent accidental removal of a connector instance.

The System Scope pertains to operations involving system statements, with common use cases including the restriction of write operations that change the ruleset of the repository.

The operation type allows FGAC to distinguish between read and write operations. Read operations are those that read data without altering its state, including data queries and queries answered by plugins. Write operations are those that write or potentially change the state of data, including data inserts, deletes, and updates handled by plugins.

FGAC in GraphDB 10.6 ensures a more nuanced approach to access control, catering to various operation scenarios and enhancing overall data security.

Streamline Node Addition in GraphDB Clusters

Significant enhancements have been made to improve the operability of the GraphDB cluster. These updates address a critical issue in cluster topology, particularly in cloud environments. Previously, the system faced challenges in seamlessly integrating new nodes in place of those that went offline. This limitation became apparent in scenarios where a failed node was replaced by a new instance with the same disk but a different hostname, preventing the new node from joining the cluster due to hostname discrepancies.

To resolve this, GraphDB 10.6 includes a revamped procedure for incorporating a node into an existing topology with pre-existing data. This approach allows nodes with altered hostnames to join a cluster without requiring the replication of all repository-related data, assuming it is already present on the node.

This enhancement not only streamlines the process of incorporating nodes into a cluster but also minimizes downtime and eliminates the necessity for file system updates.

These changes are part of our ongoing commitment to improving the GraphDB experience and ensuring robust, flexible solutions for complex data environments.

Query Like a Pro with Upgraded YASGUI in GraphDB Workbench

We are excited to announce a significant upgrade to the YASGUI (Yet Another SPARQL GUI) component in the GraphDB Workbench SPARQL editor. This major version upgrade brings a host of new features, enhancements, and bug fixes, significantly improving the user experience for working with SPARQL.

Users can now run multiple SPARQL queries concurrently and edit a SPARQL query in one tab while another query is running in a different tab. This feature is a substantial improvement, allowing for more efficient data exploration and analysis, uninterrupted workflow, and increased productivity.

This upgrade to YASGUI, comprising both YASQE (Yet Another SPARQL Query Editor) and YASR (Yet Another SPARQL Result), is part of our continued dedication to providing the best tools and features to our GraphDB users. We believe these improvements will significantly enhance your data querying capabilities and overall experience with GraphDB.

Stay Up-to-date with the Latest Versions of Third-party Libraries

As a general strategy to offer a secure and reliable product, we strive to provide up-to-date versions of third-party libraries. This includes features and bug fixes provided by the libraries and addresses newly identified public vulnerabilities.

Take advantage of all the new GraphDB 10.6 features!

New call-to-action

For more information, contact Doug Kimball, Chief Marketing Officer at Ontotext