Configuring Script Conversion Stage

The Script Conversion stage transforms Shell statements and blocks to the target equivalent Python artifacts. The input to this transformation is typically Shell scripts, which should be placed at a UFS location or uploaded directly from the local system. The output is a target equivalent Python script executable in the target environment.

To configure this stage, drag and drop the Script File stage from the transformation library onto the design workspace and then double click it.

In This Topic:

Overview
Transform
Output

Overview

In this section, you can customize the name of the Script Conversion stage and provide a suitable description as required. By default, Script Conversion is provided in the Name field. You can also provide a relevant name and description that helps you understand the purpose and scope of the stage.

Transform

Here you can configure Script files stage to transforms Shell statements and blocks to the target equivalent Python artifacts. The input to this conversion is Shell scripts in .sh or zip file format.

To configure the Script files stage, follow the steps below:

In Source Type, select the type of your source script such as Shell script.
In Input Artifacts, provide the Shell scripts for transformation via:
- Browse Files: To select the Shell scripts from the local system.
- Select From Data Source: To select the scripts from the data source. To do so, follow the steps below:
  - Click Select From Data Source.
  - Choose repository.
  - Select data source.
  - Select the entities.
  - Click to save the source data source.
In Target Type, select the target service to which you need to transform the source scripts.
Click Data Configuration.

In Output Type, the default output type for the transformation is set to Python.
In Storage Format, select DBFS to read and write input and output data.
In Default Database, select default database (Teradata, Netezza, Oracle, etc.) for the queries for which the database type is not defined in the uploaded artifacts. Selecting Not Sure will convert only those queries whose database type is available.
Click Save to update the changes.

Click to provide a preferred pipeline name.
Click to execute the pipeline. Clicking (Execute) navigates you to the listing page which shows your pipeline status as Running state. It changes its state to Success when it is completed successfully.
Click pipeline card to see report.

Output

The output of this transformation is a target-equivalent Python script executable in the target environment. A comprehensive report is generated as an output of this pipeline.

You can configure the output of this transformation for navigation to a further stage in case of any error. By default, the output configuration is set to Continue if the stage is not 100%, or that can be configured to Error, Stop, or Pause as required.

To view the Shell Script conversion report, visit Shell Script Report.