Change Log

This page will document all the changes to TigerGraph product including New Features and Bug Fixes.

Distributed Graph support, MultiGraph, and certain enterprise features are available in the Enterprise Edition only. They do not pertain to the Developer Edition.

Documentation Changes

TigerGraph 2.5.4

Release Date: 2020-04-24

Enhancements

  • New 'force' parameter to RebuildNow so that engine to start the rebuild.

  • Improved version of /abortquery so that query can be aborted more quickly

Fixed

  • Fixes in Rebuild to address broken edge count

  • RESTPP memory leak due to yaml file

  • Builtin query crashed due to missing Graph Id

  • RESTPP crash for same vertex name in the global graph

  • Resolved the distributed query hanging issue which could block rebuild and schema change

  • Core: Skewed CPU usage for high-query throughput scenarios

TigerGraph 2.5.3

Release Date: 2020-02-26

Fixes:

  • Ensure catalog data backed up before schema change

  • Support creation of two local edges with same name with one being a reverse edge

  • Support Local vertex and edge type with same name in multiple graphs in

  • Support for multi-lingual string constant in Interpret query mode

  • Upgrade to Release 2.5.2 leads to inconsistent query results

  • Compute resource usage spikes on particular node in cluster

  • GCleanUp failed to cleanup all pointers when adjusting thread

TigerGraph 2.5.2

Release Date: 2020-01-27

TigerGraph 2.5.2 is not compatible with versions prior to 2.5.1. Customers who are using Pre-2.5.1 version and intending to migrate to 2.5.2 are advised to take backup of their existing version before upgrading to 2.5.2. This will enable them to downgrade back to the original Pre-2.5.1 version if needed.

New Features

  • GPE: Increase MemoryCheck frequency based on Resource Usage

  • GPE: Abort Query if Memory usage crosses critical threshold

  • GSE: Support Log compaction as part of startup for GSE

  • GraphStudio: Support Multi-edge pair in design schema.

  • Core: Support OS RHEL 8.0 in Installer

Enhancements

  • REST: Increase the RESTPP reload timeout

  • GSQL: Change error message to specify user when default tigergraph user is dropped

  • GSQL: Make user tigergraph droppable

  • GraphStudio: Do not change layout when adding/updating/deleting vertex and edge

Fixes

  • Core: GPE crashed running distributed LDBC query

  • GST: Incorrect vertex count in TigerGraph GraphStudio

  • Core: Shuffle deadlock causing full system memory use

  • Core: Replace GASSERT with GWARN in GDataBox

  • Core: BATCH_SIZE of Kafka loader set from GSQL console doesn't work

  • GPE: Schema Change failed due to Query Install OOM

  • GSQL: Quote in string key is not escaped

  • GraphStudio: Reverse edge filter doesn't work

  • Core: Don't display LDAP password in IUM

TigerGraph 2.5.1

Release Date: 2019-11-25

Fixed

  • Core: Distributed delete affects data consistency after GPE restart

  • Core: Shuffle hangs when sendingQueue is full

  • Core: Longevity test failing due to change in memory allocator (TCMalloc)

  • GPE: Crash after upgrade from 2.4.1 to 2.5

  • GPE: Serialization error when reading from input stream

  • GPE: Query state can result in race condition inside ReadOneDelta;

  • GPE: GPE crashes when a query calls a sub-query with a write operation

  • GSE: Script to resolve delete inconsistency between GSE and GPE

  • GSE: Multiple Kafka loading jobs fail

  • GSQL: Built-in function names in GSQL are case sensitive

  • GSQL: Interpret query doesn't work when authentication is on

  • GSQL: Deadlock when graph store is being cleared and authentication is on

  • GSQL: Token authentication returning null during Global schema change

  • GSQL: SSO login failure due to missing org.apache.santuario:xmlsec library

  • GraphStudio: Vertex to edge expansion settings are not retained

  • GBAR Backup: Backup failure if loading jobs are in progress

TigerGraph 2.5.0

Release Date 2019-09-18

Changes

New and modified features and described in the TigerGraph 2.5 Release Notes.

Fixed

  • Improvements to fix possible crash, deadlock, overflow, and memory leak situations

  • Improve query performance stability

  • Fix some query string passing and parsing issues

  • Correct some inconsistencies between the documented specification and actual behavior

  • Improve robustness of Kakfa and S3 Loaders

  • Clean up files and graph properly after certain failed operations

  • Fix some installation issues

TigerGraph 2.4.1

Release Date 2019-07-23

Changes

  • To select pattern matching support in a query, the syntax is now CREATE QUERY ... SYNTAX v2 instead of CREATE QUERY ... SYNTAX("v2")

Fixed

  • GPE: Fix uint32 overflow

  • Loader: Allow temp_table to be used without flatten function

  • IDS: Disable empty UID

  • ZMQ: Fix crash on ill-formed message

  • Util: Fix Unix domain socket file not generated correctly in cron job

  • Util: Extend data size for GoutputStreamBuffer beyond 4GB

  • Connector: Fix first line is not ignored with has_header enabled

  • Connector: Fix failures on retrieving connector status

  • GSQL: Fix syntax version setting inconsistency issues

  • GSQL: Fix schema change with USING primary_id_as_attribute

  • GSQL: Fix JSON output format of requesttoken API

  • Admin Portal: Display correct counts of physical vertices and edges on each machine

TigerGraph 2.4.0

Release Date 2019-06-25

New Features

See Release Notes - TigerGraph 2.4

Fixed

  • GSQL: The built-in count() function gives the correct value in all cases.

  • GPE: startup hang

  • GSQL server start/stop command not working

  • LDAP config truncated by space

  • GSE: boolean values are not displayed correctly

  • Security issue CVE-2013-7459 caused by unused python crypto library

  • IUM status is displayed incorrectly in some cases;

TigerGraph 2.3.2

Release Date 2019-04-01

Issues

  • GSQL: The built-in count() function may give the incorrect value for clustered systems after some vertices have been deleted.

Fixed

  • GraphStudio: Send query pre-install dependency analysis result through WebSocket

  • GraphStudio: filter out improper attributes in when building filter expressions

  • GPE: fix wrong enumerator id issue

  • GPE: avoid using /tmp

  • GPE: handle exceptions for LIKE <expr>

  • GPE: Fix crash due to writing wrong size of STRING_LIST

  • GPE: Fix global schema change error which added local vertex twice

  • GSE (Developer Edition): Keep one copy of segment

TigerGraph 2.3.1

Release Date 2019-02-19

New Features

See Release Notes-TigerGraph 2.3

Issues

  • GSQL: The built-in count() function may give the incorrect value for clustered systems after some vertices have been deleted.

Fixed

  • Install: The IP list fetched by the installer could be incomplete.

  • Loading: Speed up batch-delta loading.

  • GraphStudio: Disable Install Query button for queryreader users.

  • GraphStudio: Re-initialize the database after import.

  • GraphStudio: Could not drop query with non-default username/password.

  • AdminPortal: Queries-Per-Second display didn't work if RESTPP authorization was enabled.

  • Schema change: Improve schema change stability by reducing schema change history and increasing gRPC max message limit.

  • GPE: Improve query HA stability.

  • GPE: Fix crash under certain conditions.

  • Core: Memory leak due to yamlcpp.

  • Core: compatibility issue between libc and ssh utility.

  • IUM: Fix exceptions due to legacy config entries.

TigerGraph 2.2.4

Release Date: 2018-12-13

Fixed

  • Distributed System: Fix possible deadlock and race conditions

  • GSE Storage Engine: Fix disk seek overflow

  • RESTPP: Optimize the memory consumption when system is idle

  • RESTPP: Optimize config reload time

  • GSQL: Fix query installation error with option -optimize

  • GSQL: Fix a code generation bug related to static variable

  • GSQL: Fix a compilation error when a statement is in nested if statement

  • GraphStudio: Security update for npm-run-all

  • GraphStudio: Change Help button to point to new docs.tigergraph.com site

  • Gadmin: Fix gadmin/ts3 restart and status error after changing port of TS3

TigerGraph 2.2.3

Release Date: 2018-11-30

Fixed

  • GraphStudio: Fix schema change bug (Note: In 2.2, GraphStudio now does not drop all data when making a schema change.)

  • GraphStudio: Fix display issue in Graph Explore when switch to a new graph

  • GraphStudio: Improve password security

  • GraphStudio: Modify URL to AdminPortal for better universal support

  • IUM: Fix kafka-loader configuration after cluster expansion

  • IUM: Resolve python module name conflict

  • IUM: Fix ssh_port is always 1 under bash interactive mode

  • GSE Storage Engine: Reduce memory consumption

  • RESTPP: Improve logging messages

TigerGraph 2.2

Release Date: 2018-11-05

New Features

See Release Notes-TigerGraph 2.2

Fixed

  • GraphStudio: When both a query draft and an installed query exist, Export Solution will keep the installed query code instead of the query draft

  • Admin Portal: Number of nodes in the cluster is reported as 0 when no graph yet exists

TigerGraph 2.1.8

Release Date: 2018-11-05

Issues

  • GBAR Backup fails if HA is enabled

  • GSE status shows unknown with HA enabled

  • TS3 fails to collect QPS when RESTPP Authentication is enabled (Admin Portal QPS monitor will be unavailable in this case).

  • GraphStudio: When both a query draft and an installed query exist, Export Solution will keep the installed query code instead of the query draft.

  • Admin Portal: Number of cluster nodes is reported as 0 when no graph exists.

Fixed

  • GSQL server error if schema is too large

  • In a cluster, not all servers may be aware of deleted vertices.

  • PAM limit set-up issue in installer

  • In MultiGraph, a local (FROM *, TO *) local edge has global side effects.

  • RESTPP's default API version is not set after installation

  • An engine bug which occasionally causes crash

Added

  • SSH port configuration in installer.

  • Installation script checks that the machine meets the minimum RAM (8GB) and CPU (2-core) requirements.

  • For Ubuntu 16.04/18.04, support logon with systemd service.

TigerGraph 2.1.7

Release Date: 2018-08-20

Issues

  • GBAR backup fails if HA is enabled.

  • TS3 fails to collect QPS when RESTPP Authentication is enabled (Admin Portal QPS monitor will be unavailable in this case).

  • GraphStudio: When both a query draft and an installed query exist, Export Solution will keep the installed query code instead of the query draft.

  • Admin Portal: Number of cluster nodes is reported as 0 when no graph exists.

Fixed

  • Cluster configuration with HA enabled is wrong if the number of nodes is odd (3, 5, 7, 9...).

  • GraphStudio and GSQL inconsistent checking for some keywords

  • GBAR backup and restore fail if special character is in tag name

TigerGraph 2.1.6

Release Date: 2018-08-15

Issues

  • Cluster configuration with HA enabled is wrong if the number of nodes is odd (3, 5, 7, 9...).

  • GraphStudio: When both a query draft and an installed query exist, Export Solution will keep the installed query code instead of the query draft.

  • TS3 fails to collect QPS when RESTPP Authentication is enabled (Admin Portal QPS monitor will be unavailable in this case).

  • Admin Portal: Number of cluster nodes is reported as 0 when no graph exists.

Fixed

  • GSQL null pointer exception during schema change if a directed edge is dropped but its partner reverse edge is kept.

  • Some complex attribute types cannot be correctly posted via /graph endpoint.

  • In some cases, tuple on reverse edge crashes GPE.

  • GraphStudio throws an authentication error if RESTPP authentication is enabled.

Added

  • License level control of MultiGraph functionality.

Tigergraph 2.1.5

Release Date: 2018-07-24

Known Issues

  • GSQL null pointer exception during schema change if a directed edge is dropped but its partner reverse edge is kept.

  • Some complex attribute types cannot be correctly posted via /graph endpoint.

  • In some cases, tuple on reverse edge crashes GPE.

Fixed

  • GraphStudio Export package is occasionally incomplete.

  • GSE status is always "not ready" if schema is too large.

  • Cannot modify RESTPP port configuration.

  • IUM error in a cluster when not running on node m1

Last updated