Configuring ETL Conversion Stage

The ETL Conversion stage converts ETL scripts, such as Informatica, DataStage, Ab Initio to target compatible workflows.

In this Topic:

Overview
Transform
Output

Overview

In this section, you can customize the ETL Conversion stage’s name and give a suitable description as required. By default, ETL Conversion is provided in the Name field. Provide a relevant name and description in a way that clarifies the purpose and scope of the stage.

Transform

In this section, you need to provide the graph type, source data source, target type, and output type details. Typically, the input to this transformation is a script, which should be placed at a UFS location or need to upload the file from the local system.

ETL configuration steps are defined as per the graph type selection

The table below lists the ETL sources along with the input types and supported targets for ETL Conversion.

Source	Input Type	Target
Ab Initio	KSH	Spark
		AWS Glue Studio
		AWS Glue Notebook
		Databricks Lakehouse
Informatica	XML	Spark
		Snowflake
		AWS Glue Studio
		Databricks Notebook
		Databricks Lakehouse
		Delta Live Tables
		AWS Glue Notebook
		Matillion ETL
		Redshift ELT
		Google BigQuery (Cloud Composer)
		Google BigQuery (Python)
Informatica BDM	XML	AWS Glue Notebook
Informatica BDM	XML	AWS Glue Jobs
DataStage	XML, DSX	Spark
		Snowflake
		AWS Glue Studio
		Databricks Notebook
		Databricks Lakehouse
		Matillion ETL
		AWS Glue Notebook
		Delta Live Tables
		Databricks Workflows (For DataStage Sequence Jobs)
SSIS	DTSX	Databricks Notebook
		Databricks Lakehouse
		AWS Glue Notebook
		Matillion ETL
		Spark
Talend	ITEM	AWS Glue Notebook
		Databricks Lakehouse
		AWS Glue Jobs
		Spark
IICS	XML	AWS Glue Notebook
Pentaho		Databricks Lakehouse
ODI	XML	Delta Live Tables
SnapLogic	SLP, JSON	Spark
Matillion ETL	JSON	Redshift
Matillion ETL	JSON	Databricks Notebook
SAP BODS (Available via Utility)	ATL	Databricks Notebook

Note:

When you license LeapLogic, it comes with a certain quota limit, for example upload size quota, or number of scripts which can be assessed or transformed, and likewise. The system alarms the user when the limit exceeds and highlights quota exhaustion in the pipeline reports.

To know more about how to configure the Execution stage, see Configuring Execution Stage.

Output

You can configure the output of this stage for navigation to a further stage. By default, the output configuration is set to Error if the stage is not 100% or that can be configured to Continue, Stop, and Pause as required. From the Pipeline listing page, you can view or download the report after the execution of this stage.

Note:

If you have a pipeline, the system permits you to import that existing pipeline in JSON format (as a zip file) from another environment.
To import a pipeline, follow the steps below:

Select Batch Transformation > Pipeline from the left navigation pane.
Click Import and upload the pipeline in JSON format (as a zip file).

Next:

Configuring Meta Diff