Skip to main content
Pentaho Documentation

Using the ORC Input step on the Pentaho engine

Parent article

If you are running your transformation on the Pentaho engine, use the following instructions to set up the ORC Input step.


Enter the following information in the ORC Input step fields:

Step nameSpecify the unique name of the ORC Input step on the canvas. You can customize the name or use the provided default.
Folder/File NameSpecify the fully qualified URL of the source file or folder name for the input fields. Click Browse to display the Open File window and navigate to the file or folder. For the supported file system types, see Connecting to Virtual File Systems. The Pentaho engine reads a single ORC file as input.


The Fields section contains the following items:

  • A Pass through fields from the previous step option that allows you to read the fields from the input file without redefining any of the fields.
  • A table defining data about the columns to read from the ORC file.
ORC Input step

The table in the Fields section defines the fields to read as input from the ORC file, the associated PDI field name, and the data type of the field. Enter the information for the ORC Input step fields as shown in the following table:

ORC path (ORC type)Specify the name of the field as it will appear in the ORC data file or files, and the ORC data type.
NameSpecify the name of the input field.
TypeSpecify the data type of the input field.
FormatSpecify the date format when the Type specified is Date.

You can define the fields manually, or you can provide a path to an ORC data file and click Get Fields to populate all the fields. When the fields are retrieved, the ORC type is converted into an appropriate PDI type. You can preview the data in the ORC file by clicking Preview. You can change the PDI type by using the Type drop-down or by entering the type manually.

ORC types

The ORC to PDI data type values are shown in the table below:

ORC TypePDI Type

Metadata injection support

All fields of this step support metadata injection. You can use this step with ETL metadata injection to pass metadata to your transformation at runtime.