Open Studio for Big Data
Open Studio for Data Integration
Open Studio for ESB
About this task
The last step shows the LDAP schema generated and allows you to further customize the end schema.
If needed, rename the metadata in the Name field
(metadata, by default), add a
Comment, and make further modifications, for example:
Warning: Avoid using any Java reserved keyword as a schema column name.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:
Redefine the columns by editing the relevant fields.
Add or delete a column using the and buttons.
Change the order of the columns using the and buttons.
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 LDAP directory which the schema is based on has changed, use the Guess button to generate again the schema. Note that if you customized the schema, your changes will not be retained after the Guess operation.
- Click Finish. The new schema is displayed under the relevant LDAP connection node in the Repository tree view.