Finalizing the end schema JSON of your output file
About this task
The last step of the wizard shows the end schema generated and allows you to customize
the schema according to your needs.
Procedure
If needed, rename the schema (by default, metadata) and
leave a comment.
Customize the schema if needed: add, remove, or move schema columns, export the
schema to an XML file, or replace the schema by importing an schema definition XML
file using the tool bar.
Make sure the data type in the Type column is correctly defined.
For more information regarding Java data types,
including date pattern, see Java API Specification.
Below are the commonly used Talend data types:
Object: a generic Talend data type that allows
processing data without regard to its content, for example, a data
file not otherwise supported can be processed with a tFileInputRaw
component by specifying that it has a data type of Object.
List: a space-separated list of
primitive type elements in an XML Schema definition, defined using
the xsd:list element.
Dynamic: a data type that can be set
for a single column at the end of a schema to allow processing
fields as VARCHAR(100) columns named either as ‘Column<X>’ or,
if the input includes a header, from the column names appearing in
the header. For more information, see Dynamic schema.
Document: a data type that allows
processing an entire XML document without regarding to its content.
If the JSON file which the schema is based on has been changed, click the
Guess button to generate the schema again. Note that if you
have customized the schema, the Guess feature does not retain
these changes.
Click Finish. The new file connection, along with its
schema, is displayed under the relevant File Json metadata
node in the Repository tree view.
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!
