After data is ingested to a Data Lakehouse, what happens if the data is structurally modified by a process outside of Infoworks and the metastore records are changed?

Sep 23, 2025 · The getting started chapter will walk you through the following Infoworks processes: now 6.2.1. Kubernetes-Based Deployment for AKS Configuring and Managing Environments Navigating …

Navigate to Admin section of Infoworks UI, and click on external scripts, which shows up pipeline extensions page. Click on Add an extension,and configure it as follows:

From Infoworks 2.4.0 and higher versions, metadata related to pipelines have been modified. To export a pipeline from 2.3.0 version and import it to 2.4.0 or higher versions, the following steps must be …

This service listens to the changes on the source cluster HDFS, and writes the changes in the Infoworks metastore. The incremental replicator will then replicate the changes after reading it from the metastore.

Users may observe slow ingestion performance and higher compute costs when ingesting large tables or many tables in a single job. This is often due to the default behavior where ingestion happens …

For more details, refer to our Knowledge Base and Best Practices! For help, contact our support team! (C) 2015-2022 Infoworks.io, Inc. and Confidential

For Infoworks to use Postgres PaaS, considering the variables set during the installation, the given Postgres user (set in POSTGRESDB_USERNAME) needs to have the LOGIN Role.

Before Infoworks jobs are executed, the relevant entities are locked so that conflicting jobs do not run, causing data corruption. The lock is released after the job completes.

Post installation, Infoworks can be configured and connected to the required environment from the user interface (UI). This environment can be defined from preset templates, or can also be defined as a …