Date of Release: August 2023
Enhancement
JIRA ID | Issue |
|---|---|
IPD-23719 | To capture additional logs. |
Resolved Issues
NOTE The "*" symbol next to ID refers to the issues that have been resolved in the current release.
JIRA ID | Issue |
|---|---|
IPD-23719* | Pipeline versions are getting emptied on production. |
IPD-24007* | View run is not loading workflow run page beyond recent 20 workflow runs limit. |
IPD-23613 | Last Modified Date in workflow is shown incorrectly. |
IPD-23636 | Pipeline Jobs list not visible. |
IPD-23663 | File Archival process is not archiving files with only header records post upgrade to 5.4. |
IPD-23647 | The staging table created by Infoworks during pipeline build will be persisted in the BigQuery if the load job fails. |
IPD-23754 | Records were missing in the BigQuery target table even though the pipeline was completed successfully. |
IPD-23822 | Schema name is null/empty for incremental pipelines in BigQuery environment on using use_ingestion_time_as_watermark key |
IPD-23831 | Around 50% of the pipeline documents have pipeline id and active version id same in production. |
IPD-23899 | Refresh token not generated for newly created users in 5.4.1.6. |
IPD-23515 | Ingestion job on BQ environment is running queries on GCP project present in service account JSON instead of parent_project |
IPD-23526 | Issues while using partitioned externally created BQ table in our pipelines. |
IPD-23452 | Rest API - Bug in 5.4.1 config migration where few keys are in camelCase (should be in snake_case). |
IPD-23418 | BigQuery pipelines will not be failing with java.lang.IllegalArgumentException: Provided query is null or empty error after the upgrade. |
IPD-23327 | Fixed the Issue where Inactive spark advanced configs are taking effect in 5.4.1.4. |
IPD-23263 | Infoworks Scheduler not submitting jobs on high load time duration. |
IPD-23498 | Project ID field issue on the teradata source configured on the BigQuery data environment. |
IPD-23216 | Unable to unlock locked entities. |
IPD-22964 | The |
IPD-22983 | For a source table fetched from a Confluent source with incremental mode as Append, the pipeline source query does not bring the entire dataset every time anymore irrespective of the provided query. |
IPD-22963 | For the 5.3.x and 5.4.x versions, when the Incremental Load is enabled and the Sync Type is set to append, the second build of the pipeline does not copy the duplicate records anymore. |
IPD-22038 | Fixed the unlock functionality for the Admin users. |
IPD-22113 | You can now create pipelines via the API by using Environment Name, Environment Storage Name, and Environment Compute Template Name. |
IPD-22817 | The |
IPD-22721 | For Confluent Kafka source, the |
IPD-22615 | The Partition and the Clustering details are now appearing in the BigQuery table created via Infoworks pipeline. |
IPD-22036 | Pipeline build now succeeds even when the target table for the BigQuery external target already exists and is clustered. |
IPD-22090 | For the Delimited File target, the timestamp format can be configured as per the user requirements. This will be applicable for all the timestamp columns for that table.
|
IPD-22351 | Infoworks has added advanced configuration for setting BigQuery Session Project IDs for Data Transformation and Ingestion jobs (dt_bigquery_session_project_id/ingestion_bigquery_session_project_id) |
IPD-21449 | The Import SQL API is now picking the correct table (even if a table with the same schema/table name is present in multiple data environments). |
IPD-21534 | The Initialize & Ingest and Truncate jobs can now reset the value of the |
IPD-21584 | The Import SQL command is now able to fetch queries that contain backtick (`). |
IPD-21700 | Fixed the pipeline deletion issue. |
IPD-21792 | The duplicate tables are not allowed to be onboarded anymore on HIVE Metadata sync source. |
Upgrade
Assuming IW_HOME variable is set to /opt/infoworks
Prerequisite
To support rollback after metadata migration, you need to take backup of metadata. Following are the steps:
Step 1: Install/Download MongoDB tool: mongodump. (if needed).
Step 2: Create a directory to store the database backup dump using the below command.
Step 3: Use the below command to take a dump (backup) of the databases from the mongodb server.
If MongoDB is hosted on Atlas
If MongoDB is installed with Infoworks on the same VM
Procedure
For upgrading from 5.4.1/5.4.1.x to 5.4.1.8, execute the following commands:
Step 1: Use the deployer to upgrade from 5.4.1 to 5.4.1.8.
Step 2: Goto iw_home/scripts folder of the test machine.
Step 3: To ensure that there is no pre-existing update script, execute the following command:
[[ -f update_5.4.1.8.sh ]] && rm update_5.4.1.8.sh
Step 4: Download the update_5.4.1.8.sh
wget https://iw-saas-setup.s3.us-west-2.amazonaws.com/5.4/update_5.4.1.8.sh
Step 5: Give update.sh executable permission
chmod +x update_5.4.1.8.sh
Step 6 (Optional): This patch requires Mongo Metadata to be migrated. To export the environment variable, run export METADB_MIGRATION=Y. This ensures that the metadata will be migrated, else run export METADB_MIGRATION=N.
Alternatively, you can enter it in the prompt while running the script.
Step 7: Update the package to the hotfix source iw_home/bin/env.sh
./update_5.4.1.8.sh -v 5.4.1.8-ubuntu2004
You will receive a "Please select whether metadb migration needs to be done([Y]/N)" message. If you need to perform metadb migration, enter Y, else, enter N.
Rollback
Prerequisite
To rollback the migrated metadata:
Step 1: Install/Download MongoDB tool: mongorestore. (if needed)
Step 2: Switch to the directory where the backup is saved on the local system.
Step 3: Use the below command to restore the dump (backup) of the databases to the Mongodb Server.
If MongoDB is hosted on Atlas
If MongoDB is installed with Infoworks on the same VM
Procedure
To go back to previous checkpoint version:
Step 1: In a web browser, go to your Infoworks system, scroll-down to the bottom, and click the Infoworks icon.
Step 2: The Infoworks Manifest Information page opens in a new tab. Scroll down and check the Last Checkpoint Version.
Step 3: ssh to Infoworks VM and switch to {{IW_USER}}.
Step 4: Initialize the variables in the bash shell.
full_version=5.4.1.8
major_version=$(echo $full_version | cut -d "." -f 1-2)
previous_version=<Previous Version> # Last Checkpoint Version from step 1
os_suffix=<OS Suffix> # One of [ ubuntu2004 amazonlinux2 rhel8 ]
Step 5: Download the required deployer for the current applied patch.
https://iw-saas-setup.s3-us-west-2.amazonaws.com/${major_version}/deploy_${full_version}.tar.gz
Step 6: Execute the SCP command for the above mentioned files to the following path.
NOTE Remove the previously downloaded copy of deploy_${full_version}.tar.gz file in ${IW_HOME}/scripts/ directory.
${IW_HOME}/scripts/.
Step 7: Extract the deployed tar file in case it does not exist.
cd ${IW_HOME}/scripts
[[ -d iw-installer ]] && rm -rf iw-installer
tar xzf deploy_${full_version}.tar.gz
cd iw-installer
Step 8: Initialize the environment variables.
source ${IW_HOME}/bin/env.sh
export IW_PLATFORM=saas
Step 9: Run the Rollback command.
./rollback.sh -v ${previous_version}-${os_suffix}