You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of the static schema is to provide a static way to provide tabular layouts to input and output transforms in an Apache Hop pipeline.
Static schemas should:
Exist per project/customer
Initially apply to a selected set of input and output transforms (CSV FIle Input, Excel Input, Microsoft Excel Writer, Text file input, Text file output)
Transforms that use a static schema will incorporate the schema definition in the transform’s metadata (embedded in the pipeline’s XML serialization). Also, a new transform called “Schema Mapping” will allow an Apache Hop pipeline developer to map a pipeline stream to a static schema layout.
Issue Priority
Priority: 3
Issue Component
Component: Transforms
The text was updated successfully, but these errors were encountered:
It's the first step to catalog integration, let's say you require a specific schema for your output CSV files you can define them and map your stream to match this definition
What would you like to happen?
The purpose of the static schema is to provide a static way to provide tabular layouts to input and output transforms in an Apache Hop pipeline.
Static schemas should:
Transforms that use a static schema will incorporate the schema definition in the transform’s metadata (embedded in the pipeline’s XML serialization). Also, a new transform called “Schema Mapping” will allow an Apache Hop pipeline developer to map a pipeline stream to a static schema layout.
Issue Priority
Priority: 3
Issue Component
Component: Transforms
The text was updated successfully, but these errors were encountered: