After you have completed the upgrade of the software on the Trifacta node, you may need to migrate some pre-upgrade configuration values to the new environment.
These migrations steps should be performed whenever you upgrade between any two versions, even if you have not modified any configuration values. If there are no migrations to be performed, the process does not harm.
Do not restart the software until instructed to do so.
Create New Databases
NOTE: Please stop the databases before you create the new ones.
After upgrade, you may need to create new databases depending on your pre- and post-upgrade releases.
Tip: This step is harmless if there are no new databases to create for this upgrade.
For more information, see Install Databases in the Databases Guide.
Modify pg_hba.conf (PostgreSQL only)
Any new databases must be referenced in
Locate the sample Postgres configuration file:
- If you are upgrading and have customizations in your existing version, you must apply the edits in the above to the following file. Otherwise, overwrite the following file with the above one based on your operating system:
- CentOS/RHEL dir:
- CentOS/RHEL dir:
SAMPLEfile, copy the appropriate declarations and paste them into the production
pg_hba.conffile above any other declarations.
For more information on the declarations, see Configure the Databases in the Databases Guide.
Save the file.
- Restart PostgreSQL.
Before you run the following script, please create a backup of
/opt/trifacta/conf/trifacta-conf.jsonin its current state. This backup is used to restore values after you have completed the script execution. It is important that you take the backup at this time.
Run the following script, which creates any new databases and users and roles for accessing them.
- See Create Databases and Users in the Databases Guide.
/opt/trifacta/conf/trifacta-conf.jsonfrom the backup you created of that file.
- Restart the databases.
Data Service property updates for Release 7.1
NOTE: This step applies if you are upgrading from a pre-Release 7.1 to Release 7.1 or later.
After the platform has been upgraded to Release 7.1, some of the migrated properties are submitted from the
application.properties file used to configure the data service. These properties are no longer directly editable by users.
If you have modified property values in
application.properties, you must migrate your old values into the new
application.properties file to retain your customized property values. The migration process gathers these values from the
application.properties file and inserts them as the new values in the Configuration Service database. If you fail to complete these steps and need to retain our change property values, please contact Trifacta Customer Success Services.
Login to the Trifacta node. Navigate to the following directory:
Perform a diff between the following two files:
application.properties(file used during migration)
Merge property values:
NOTE: Property values in
application.properties.rpmsavemust be migrated into
application.propertiesfor inclusion in the Configuration Service database or (if not migrated) preservation in the upgraded deployment.
- Save the file. You should archive the
rpmsaveversion to a location outside of the }Trifacta deployment.
- Complete the rest of the steps to migrate your configuration in the sections below.
- When the platform is restarted at the end of the migration process, the property values in your pre-upgrade
application.propertiesare inserted as the new values for the properties maintained in the Configuration Service database.
Migrate Values to Configuration Service
During the upgrade process, some configuration properties are automatically migrated to the Configuration Service. In most cases, these properties are automatically enabled and are hidden from view. For more information, see Changes to Configuration in the Release Notes.
Merge Customized Configuration Files
After upgrading the software, you should scan the install directory tree for
.rpmnew files. These files are the default versions of configuration files from the new software distribution that were written in parallel to a modified configuration file from the previous version.
Review the following directories and files for
NOTE: Do not perform manual migrations of
/opt/trifacta/conf/trifacta-conf.json. Migrations of this file are automatically performed as part of the upgrade process.
- Configuration settings from the old files must be explicitly merged into the new files (
- Remove old files from Trifacta install directory:
- Create a directory outside of the Trifacta install directory.
Move all of the config files from the previous version into this directory.
NOTE: Do not leave the old config files in the install directory. There should not be multiple configuration files of the same kind.
- Rename these old config files outside of the directory to include a
.backupextension. You could also put the version number of the config file.
.rpmnewextension must be removed from the new files.
- Your previous configuration should be carried forward into the new version.
Migrate properties for remote databases
If you have installed the Trifacta databases on a remote server, you must repopulate the values in
trifacta-conf.jsonfor the remote host, port, and other connection properties for your remote databases. Properties must also be populated for any new databases that were created as part of this upgrade process.
For more information, see Database Parameter Reference.
While the platform can now start, you should avoid doing so until have you completed all required steps in this guide.
NOTE: Please be sure to review any post-upgrade instructions and perform any post-upgrade cleanup in the following sections.
This page has no comments.