A new file in the python directory called G2SetupConfig.py migrates your config into the Senzing database and should be run after the upgrade but before config upgrades. Once complete you will no longer edit the g2config.json file or specify G2CONFIGFILE in your G2Module.ini. The API will pull the active configuration from the database and G2ConfigTool.py will load/modify/save the config from/to the database also.
This allows for all applications to share the same configuration and, if coded to support it, applications can automatically load the new configuration while running -- the REST API server and stream loader projects already do this.
To accomplish this migration, from the project directory originally created by G2CreateProject.py, run:
If you are upgrading from 1.11 (not 1.11.2) first process the/opt/senzing/g2/resources/config/g2core-config-upgrade-1.11-to-1.11.2.gtc configuration upgrade file. This will upgrade the configuration version from 4 to 4.1.
Use the G2ConfigTool.py to apply these changes:
python3 G2ConfigTool.py -f /opt/senzing/g2/resources/config/g2core-config-upgrade-1.11-to-1.11.2.gtc
Once your configuration version is at 4.1, process the/opt/senzing/g2/resources/config/g2core-config-upgrade-1.11-to-1.11.2.gtc configuration upgrade file. It adds a small principle change to improve quality in some data scenarios. This will upgrade the configuration version from 4.1 to 5.
Use the G2ConfigTool.py utility to apply these changes.
python3 G2ConfigTool.py -f /opt/senzing/g2/resources/config/g2core-config-upgrade-1.11.2-to-1.12.gtc
If you do not apply this update you will get an error on start-up that your configuration needs to be version 5.
There are no new schema changes.