Upgrading from Senzing API 1.10 to 1.11

Configuration Changes

The g2/data/g2core-config-upgrade-1.10-to-1.11.gtc file contains the commands to update your g2config.json to the new version.  It adds a small principle change to improve quality in some data scenarios.

Please use the G2ConfigTool.py to apply these changes.

If you do not apply this update you will get an error on start-up that your configuration needs to be version 4. 

Schema changes

A new CONFIG_ID is added to the DSRC_RECORD table.  On certain databases (e.g. MySQL <8.0.13) this can be a very expensive operation so please consult your DBA.

After installing Senzing 1.11, find the g2core-schema-<DB Type>-upgrade-1.10-to-1.11.sql file appropriate for your database and apply it to your database.  Since it is just adding an empty table and index it should be instantaneous.

This new tables supports the G2Engine API's ability to share configurations and store installation variable such as configuration versions.

Other items

The YUM and APT repositories are now public and live.  This is the recommended way to install Senzing and the .tgz file method will be removed in the coming months.  Please see this article for more information.

For API users leveraging the Community REST server and/or stream loader, we can't emphasize enough how valuable it is to leverage the new JSON config in the DB functionality.  This allows for multiple nodes to automatically update their configurations without having to be restarted.  If you want help in migrating please contact support and we will walk you through it.