The TigerGraph 3.1.5 update includes a fix for a bug that affects all versions of TigerGraph from 3.0.0 to 3.1.4. Since the bug has the potential to cause schema inconsistency issues and interrupt database services, we strongly advise all customers who are using an affected version of TigerGraph to upgrade to TigerGraph 3.1.5 or later.
This advisory applies to all versions of TigerGraph from 3.0.0 to 3.1.4:
When running a schema change job, schema inconsistency issues might occur if the database catalog includes duplicate vertex or edge type names. Database services will remain unavailable until the schema inconsistency issues are fixed.
If you run into this issue, please contact support@tigergraph for help.
Before upgrading to TigerGraph 3.1.5/3.1.6, it is essential that you follow the steps below to validate your database catalog. Failure to perform the validation can lead to schema inconsistency issues.
This procedure should be performed under the TigerGraph Linux user.
Run the commands below to download and extract the catalog validation package:
After you extract the tar file, run the following script to validate your database catalog:
If the script outputs Successfully finished verifying catalog
, you can proceed to upgrade to 3.1.5/6. See Updrading an Existing Installation for upgrade instructions.
If the validation fails, please gather the following files and open a support ticket with TigerGraph.
The tar file produced from compressing the gsql_check_catalog
folder:
The graph store configuration YAML file located at:
Please open a ticket with the following title: "GSQL 3.1.5 upgrade check verification failed" and set its priority level as High.
If you have restrictions in your environment that disallow you from sharing these files, please note so in the ticket and share your availability for a Zoom call with our support team.