×

☰ Table of Contents

Release Notes for TigerGraph Platform version 1.2

MENU
MENU

TigerGraph Docs : Release Notes for TigerGraph Platform version 1.2

Document updated:

New Features

There is one major addition to the TigerGraph platform in v1.2: MultiGraph with Graph-Based Access Control

MultiGraph with Graph-Based Access Control

TigerGraph 1.2 allows one TigerGraph instance can manage multiple graphs, each with its own set of user privileges. MultiGraph is offered as an add-on service. MultiGraph enables several use cases:

  • Multiple Tenancy : completely separate data sets with separate sets of users.
  • Overlapping graph schemas for shared data : Allow some data to reside in more than one graph: real-time sharing.
  • Fine-grained access control: Two graphs with the same data can have two different sets of queries and access privileges.

To support the new MultiGraph capabilities, a few changes to the previous specifications are necessary. These changes affect all users, even if only a single graph is deployed . We advise users who are upgrading from a previous version to read the bulletin: MultiGraph - An Overview .

New Commands and Specifications

See MultiGraph - An Overview

Changes to Existing Specifications

  • User roles are granted or revoked on a per-graph basis.
  • A user can work with only one graph at a time. The user must set their working graph, either with the -g option for the GSQL command, or with the USE GRAPH statement.  This requirement holds even when there is only a single graph in existence.
  • The privileges of the admin and architect roles have been reduced. They can no longer CREATE or DROP a VERTEX/EDGE/GRAPH.  However, they can CREATE and RUN a SCHEMA_CHANGE JOB, which accomplishes much the same thing.
  • The admin and architect roles can no longer run DROP ALL or CLEAR GRAPH STORE.
  • DROP GRAPH <gname> only drops vertex and edge types which are exclusive to that graph.  It does not drop shared types.
  • When a new user is created, previously the user began with the public role. Now, the new user has no role until assigned one.

Other Changes

GSQL Language

  • NEW : Container type attributes (e.g., a LIST or SET) can be updated (assigned a new value) in a query.  Previously, only simple type attributes could be updated. See the examples of Update statement in the Data Modification Statements chapter of the GSQL Language Reference Part 2 - Querying

  • REMOVED : In the CREATE VERTEX schema definition statement, the WITH STATS = "outdegree" option is no longer supported. The "outdegree_by_edgetype" and "null" options are still available.

System Configuration

  • CHANGED : The default TCP/IP port numbers for GraphStudio and its related services have changed, to avoid the possibility of conflict with other services. These port numbers are not mandatory. As before, users can set the port number with gadmin --configure

    • GraphStudio (and other Nginx services): from 44240 to 14240
    • GraphStudio.WebSocket.Port: from 44241 to 14241
    • GraphStudio.Web.Private_port: from 44242 to 14242

GraphStudio UI

  • NEW : In the Map Data to Graph step, users can now load a constant value (string or numeric). The constant value can either be applied directly to an attribute, or it can be one input of a token function.

User Authentication

  • REMOVED : The gsql -s option is dropped.  A secret cannot be used in place of a password.

Bug Fix

  • REST API output format for tuple type data is now consistent with standard JSON.


Updating to v1.2

Always refer to all the incremental Release Notes between your current version and your target version before undertaking an Upgrade.  Pay attention to changes in features and compatibility of the data and application files. Contact support@tigergraph.com if you have any questions.




Copyright © 2018 TigerGraph. All Rights Reserved.