Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Copying schema columns from Talend Studio components or the Generic Schema Editor

Copy schema columns from a Talend Studio component schema or the Generic Schema Editor and paste them as elements in a hierarchical mapper structure.

About this task

You can reuse schema columns from Talend Studio component schemas or from the Generic Schema Editor by copying them and pasting them into hierarchical mapper structures. The schema columns are automatically converted to structure elements with the appropriate data types.

Procedure

  1. In Talend Studio, right-click one or more schema columns in a component schema or in the Generic Schema Editor, and click Copy.
  2. In the Hierarchical Mapper, open the structure where you want to add the elements.
  3. To paste the schema columns as child elements, right-click the parent element and click Paste from Studio schema.
    If you copy schema columns in the Generic Schema Editor, this action is available in the TDM Structure Editor. The schema columns are added as child elements under the selected parent.
  4. To paste the schema columns as sibling elements, right-click an element and click Paste as Sibling from Studio schema.
    The schema columns are added at the same level as the selected element.

Results

The copied schema columns are converted to structure elements with data types mapped as follows:

Component schema type Hierarchical mapper structure type
Boolean Boolean
Byte Byte (8)
Character Character
String String
Date DateTime
Double Double
Float Float
Integer Integer (32)
Long Integer (64)
Short Integer (16)
BigDecimal Decimal
Information noteNote: Schema columns with unsupported data types are skipped during the paste operation.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here