v5.4.2.2

Date of Release: June 2023

Resolved Issues

NOTE The "*" symbol next to ID refers to the issues that have been resolved in the current release.

JIRA ID	Issue
IPD-22755*	The GET and PUT methods now returns JSON table containing the `user_managed_target_path` key for user-managed tables.
IPD-22760*	The SQL Import now correctly executes the GROUP BY ROLLUP queries.
IPD-22857*	The Segment Load job with multi-watermark column now completes without any delay.
IPD-21954	While importing the BTEQs with table joins containing the InNotIn condition, the `ClassCastException failure - io.infoworks.awb.pipeline.dto.InNotInNode to io.infoworks.awb.pipeline.dto.JoinNode` error does not appear anymore.
IPD-21955	While parsing the BTEQs with UPDATE, GROUP BY, and HAVING conditions into the SQL pipelines, the `ClassCastException failure - org.apache.calcite.sql.SqlIdentifier to org.apache.calcite.sql.SqlBasicCall` error does not appear anymore.
IPD-21956	Each expression value in the Select SQL query is now assigned to a unique derived column.
IPD-22025	If you set the `dt_skip_sql_validation` configuration and then delete it, the configuration will be set to false (default value).
IPD-22032	The `importSql` REST API is now working correctly.
IPD-22034	The non-visual Infoworks SQL Pipeline can now execute the SnowSQL query.
IPD-22037	The user-managed table options are now available for streaming sources in the CDW environment.
IPD-22048	During the workflow migration, the dropdown under the Interactive Compute Template Mapping section is now enabled.
IPD-22051	Input ports of the Union node are getting assigned correctly during the pipeline validation.
IPD-22076	The Sync to External Target functionality for the Delimited files is now successfully displaying the data connection options.
IPD-22332	User can now set the `active_version_id` using REST API.
IPD-22421	The import workflow configuration migration API now includes pipeline version mapping.

Upgrade

Prerequisites

NOTE Before going through the below mentioned prerequisites for this section, ensure that all the Prerequisites for Installing Infoworks on AKS are validated.

Ensure the current deployment’s chart is present in /opt/infoworks.
Python 3.8 or later version with the pip module is installed in the Bastion VM.
Stable internet connectivity on the Bastion VM to download the required python packages from the python repository during installation/upgrades.
Validate that the version of the old chart is 5.4.2.1.

 Command 
    
xxxxxxxxxx
 
cat /opt/infoworks/iw-k8s-installer/infoworks/Chart.yaml | grep appVersion
Copy

 Output 
    
xxxxxxxxxx
 
appVersion: 5.4.2.1
Copy


	Ensure to take backup of MongoDB Atlas and PostgresDB PaaS. In case you don't take the backup, jobs will fail after the rollback operation. For more information, refer to the MongoDB Backup and PostgresDB PaaS Backup

Upgrade Instructions

To upgrade Infoworks on Kubernetes:


	It is assumed that the existing chart is placed in the /opt/infoworks directory and the user has the access permission.

 Command 
    
xxxxxxxxxx
 
export IW_HOME="/opt/infoworks"
Copy

Before selecting the type of upgrade execute the following commands.

Step 1: Create the required directories and change the path to that directory.

 Command 
    
xxxxxxxxxx
 
mkdir -p $IW_HOME/downloadscd $IW_HOME/downloads
Copy

Internet-free Upgrade

NOTE If you are upgrading via Internet-based procedure, skip to the next section.

Step 1: Download the upgrade tar files shared by the Infoworks team to the Bastion (Jump host) VM and place it under $IW_HOME/downloads.

Step 2: To configure Internet-free upgrade, execute the following command:

 Command 
    
xxxxxxxxxx
 
export INTERNET_FREE=true
Copy

Internet-based Upgrade

Step 1: Download the Update script tar file.

 Command 
    
xxxxxxxxxx
 
wget https://iw-saas-setup.s3-us-west-2.amazonaws.com/5.4/iwx_updater_k8s_5.4.2.2.tar.gz
Copy

Common Steps for Both Internet-free and Internet-based

NOTE Once you have selected the type of upgrade, the below mentioned steps are common for both Internet-free and Internet-based.

Step 1: Extract the iwx_updater _k8s_5.4.2.2 tar.gz under $IW_HOME/downloads.


	Do not extract the tar file to /opt/infoworks/iw-k8s-installer as it would result in loss of data.

 Bash 
    
xxxxxxxxxx
 
tar xzvf iwx_updater_k8s_5.4.2.2.tar.gz
Copy

This should create two new files as follows - update-k8s.sh and configure.sh.

Step 2: Run the script.

 Command 
    
xxxxxxxxxx
 
./update-k8s.sh -v 5.4.2.2
Copy

NOTE At the end of the above command's execution, if you want to run helm upgrade manually, then type N and press Enter. There is a 30-second timeout set to abandon the deployment of the upgraded version. If no input is received within the timeout duration, the deployment is triggered.

 Output 
    
​x
 
helm upgrade 531 /opt/infoworks/iw-k8s-installer/infoworks -n aks-upgrade-540 -f /opt/infoworks/iw-k8s-installer/infoworks/values.yaml ​Enter N to skip running the above command to upgrade the helm deployment. (timeout: 30 seconds): NUpgrade success
Copy

Step 3: Once the upgrade is successful, execute the following command to restart the hangman deployment.

 Command 
    
xxxxxxxxxx
 
kubectl rollout restart deployment <release_name>-hangman -n <namespace_name>
Copy

NOTE Replace the <release_name> and <namespace_name> in the above mentioned command with the release and namespace that you are currently using.

Step 4: To verify if hangman has successfully restarted, run the following command and make sure all the pods are in the Running state.

 Command 
    
xxxxxxxxxx
 
kubectl get pods -n <namespace_name>
Copy

Step 5 (Applicable only for Databricks Persistent Clusters): A change in the Infoworks jar requires libraries being uninstalled and cluster restart. Without this step, there will be stale jars. Perform the following steps:

(i) Go to the Databricks workspace, navigate to the Compute page, and select the cluster that has stale jars.

(ii) In the Libraries tab, select all the Infoworks jars and click Uninstall.

(iii) From Infoworks UI or Databricks dashboard, select Restart Cluster.

Rollback

Prerequisites

Before executing the rollback script, ensure that IW_HOME variable is set.
Assuming Infoworks home directory is /opt/infoworks, run the below command to set the IW_HOME variable.
Validate that the version of the old chart is 5.4.2.2

 Command 
    
xxxxxxxxxx
 
export IW_HOME=/opt/infoworks
Copy

Ensure the current deployment’s chart is present in /opt/infoworks.
Execute the below command to check the appVersion.

 Command 
    
xxxxxxxxxx
 
cat $IW_HOME/iw-k8s-installer/infoworks/Chart.yaml | grep appVersion
Copy

 Output 
    
xxxxxxxxxx
 
appVersion: 5.4.2.2
Copy


	Ensure to restore MongoDB Atlas and PostgresDB PaaS. In case you don't take the backup, jobs will fail after the restore operation. For more information, refer to the MongoDB Restore and PostgresDB Restore.

Rollback Instructions

NOTE Since IW_HOME has been exported in the Prerequisites section mentioned above, the following steps can be executed from any location for users with read/write access to the aforementioned IW_HOME.

Step 1: Download the rollback script.

 Command 
    
xxxxxxxxxx
 
wget https://iw-saas-setup.s3.us-west-2.amazonaws.com/5.4/rollback-k8s.sh
Copy

Step 2: Place the Update script in the same directory as that of the existing iw-k8s-installer.

Step 3: Ensure you have permission to the $IW_HOME directory.

Step 4: Give executable permission to the rollback script using the below command.

 Command 
    
xxxxxxxxxx
 
chmod +x rollback-k8s.sh
Copy

Step 5: Run the script.

 Command 
    
xxxxxxxxxx
 
./rollback-k8s.sh -v 5.4.2.1
Copy

Step 6: You will receive the following prompt, "Enter N to skip running the above command to upgrade the helm deployment. (timeout: 30 seconds): ", type Y and press Enter.

NOTE If you want to run helm upgrade manually, then type N and press Enter.

 Prompt 
    
xxxxxxxxxx
 
Enter N to skip running the above command to upgrade the helm deployment. (timeout: 30 seconds): Y
Copy

NOTE There is a 30-second timeout set to abandon the deployment of the downgraded version. If no input is received within the timeout duration, the deployment is triggered.

Last updated on

Was this page helpful?