Copyright © 2019. All Rights Reserved.
Multiple Tenancy : Use one TigerGraph instance to support several completely separate data sets, each with its own set of users. Each user community cannot see the other user communities or other data sets.
Fine-grained privileges on the same set of data : Role-based access control, available on single graphs, grants permission for the privilege to run queries (include data modification queries). In a single graph scheme, there is not a way to say "Query X can be run by some users but not by others." Using multiple graphs defined over the same set of data, each graph can have its own set of queries and own set of users, in effect customizing who can run which queries.
Overlapping graphs : Graphs can partially overlap, to enable a combination of shared and private data.
Hierarchical subgraphs : A Graph X can be defined to cover the domains of Graphs Y and Z, that is, Graph X = (Graph Y) U (Graph Z). This provides an interesting way to describe a data partitioning or parent-child structure. (This is not the same as defining sub-classes of data types; data types are still independent.)
Beginning with Version 1.2, one TigerGraph instance can manage multiple graphs, each with its own set of user privileges. This first-of-its-kind capability, dubbed MultiGraph, is available as an optional service in the Enterprise Edition of the TigerGraph platform. MultiGraph enables several powerful use cases:
If you implement only one graph now, you can upgrade to MultiGraph and add additional graphs at any time, without having to redo your existing design.
A graph is a defined as a set of vertex types and edge types. More precisely, it is all the vertices and edges of that collection of types. The domain of a graph is its set of vertex types and edge types. Each graph contains its own data loading jobs and queries, which do not affect and are not visible to other graphs.
The TigerGraph system includes several predefined roles. Each role is a fixed and logical set of privileges to perform operations. In order to access a graph, a user must be granted a role on that graph. Without a role, a user has no meaningful access.
Previously, there was only one graph, and so all users were automatically able to use that graph.
Note that the CREATE commands for queries, loading jobs, and schema_change jobs have always required that the graph name be specified, even when there was support for only one graph. Now, it is clear that these definitions are graph-specific.
If you are a user of an earlier TigerGraph system (v1.1 or earlier), please note the following specifications have changed.
Set the working graph in GSQL: You must always set the working graph, either using the -g flag with the gsql command, or by using the USE GRAPH command.
RESTPP Endpoint changes: Endpoints which pertain to the graph data have been modified to include the name of the graph in the request URL. See RESTPP API User Guide .
User Authentication secrets and tokens: The way in which secrets and tokens are created and used has changed, in order to follow OAuth standards more closely. See Managing User Privileges and Authentication.
Changes to privileges of certain roles: If you had been using only the single default user with admin privilege, you will not notice any difference. That user has been promoted to superuser status. If you are making use of users with different roles, note the following changes in privileges:
A new top-level role, superuser , is defined. The superuser has admin privilege on all graphs, and is the only role who can create and modify shared vertex types, shared edge types, and graphs.
The architect role is renamed designer .
The public role is renamed observer .
The following commands are now shifted from admin and designer roles to the superuser role:
CREATE / DROP VERTEX|EDGE|GRAPH
CLEAR GRAPH STORE
Newly created users no longer automatically have the observer role. They have no role until explicitly granted one.
In the CREATE VERTEX statement, the WITH STATS option "outdegree" is no longer available. "outdegree_by_edgetype" is still supported and is the default.
There are many other details about using the MultiGraph feature, especially if your application has mulitple users with different roles. In the documentation, the Multiple Graph logo is placed next to relevant topics:
The following commands are new. This section provides only a summary list. For full details and examples, see the main documentation for the relevant topics.
For all users
Sets the given graph as the user's working graph.
Must be set to have privilege to create and assign global vertex and edge types.