Documentation
Talend Import Utility.
The Odara ETL Talend Import Utility (Beta): upload a Talend project export, read its X-Ray, approve what each job does and import the jobs as pipelines and Maestros.
16. Talend Import Utility (Beta)
16.1 What it does
The Import Utility reads a Talend project export and proposes Odara pipelines that you review before anything is built. Open it from the page menu in the top bar → Import Utility. It is in Beta.
16.2 Upload, X-Ray, Understand, Import
- Upload the project export: the
.zipfrom Talend Studio, or the project folder zipped from git. - X-Ray: a report of every job and component, families of similar jobs, and the effort to migrate.
- Understand: the AI — the provider you configured, with your key — explains what each job does: its purpose, steps, business rules, checks and open questions. You correct it and approve it.
- Import: jobs become Odara pipelines; jobs that only call other jobs become Maestros. Anything not supported is reported, not guessed.
Examples from the importer's mapping table:
| Talend component | Odara node |
|---|---|
tDBInput / tPostgresqlInput | PostgreSQL Read |
tFileInputDelimited | CSV Source |
tMap | Mapper |
tAggregateRow | SQL |
tJavaRow / tJava | Python |
tRunJob | Maestro step |
16.3 What to expect
- It is a Beta: review every proposed pipeline, and test it against your data before replacing a Talend job.
- Explaining jobs needs an AI provider configured in AI Settings; the X-Ray works without one.
- To keep running an exported Talend job as it is while you migrate, use the Run External Job node.