Skip to main content Skip to complementary content

Exporting Structures

About this task

Talend Data Mapper provides you with the possibility to export your Structures as CSV files, Java classes, Avro files, or XML Studio Schema files to enable you to work with the exported files in external tools.

The procedure for all types of output file is more or less the same. Any particularities based on the type of structure are specified below.

To export Structures, do the following:

Procedure

  1. Click File > Export to open the Export window.
  2. Expand Data Mapper and select either of the following: as appropriate, then click Next.
    • CSV Export
    • Java Export
    • Avro Export
    • Studio Schema Export (technical preview)
      Information noteWarning: Studio Schema Export is in a technical preview status and an experimental feature. This feature might stop working or get removed without notice. It is highly recommended not to use Studio Schema Export in production. For more information, refer to Studio Schema Exporter.
  3. In the window that opens, expand your project in the left-hand pane and select the Structures checkbox.
  4. Select the checkboxes in the right-hand window that correspond to the Structures you want to export.
  5. In the To directory field, select the directory to which you want to export by clicking Browse, browsing to the target directory or clicking Make New Folder if the directory does not already exist, and then clicking OK.
  6. [For Java classes] In the Java package name field, enter a name for the package you are going to create.
  7. [For Avro files] In the Avro namespace field, enter a name for the Avro namespace.
  8. [For Avro files] Click the Include documentation checkbox to add the description of structure elements in the exported Avro schema.
  9. [For Studio Schema] Click the Include documentation checkbox to include the comments fields in the resulting Studio Schema.
  10. Click Finish to complete the process.

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!