tHMap (Data Mapper) version management for Maps and Structures

[SMR040]

Hi community,

The Data Mapper is a very powerful product and because of that I use it very often. But one thing I could not find any documentation about is the versioning for Maps and Structures. Of course I can duplicate existing Maps etc and add _0.1 for example but this will create a huge list eventually. Also I understand that when you use a source file like with APIs you can use OAS spec and keep versions on the input side.

But what I am looking for is to version the Maps and Structures. The reason for that is because that for every new version of a job the same version of the Map is used. So it is not possible to revert changes when going back to a previous version of the job.

Thanks!

[Anonymous]

While the file versioning is still supported in Talend Studio, we would advise using Git versioning moving forward.

[SMR040]

thanks for your response. How would you see that with Maps and Structures? For example how can I make a distinction in the versions of mapping and relate that version with a specific job version?

Would help if you gave a practical example.

Thanks

[SMR040]

@Richard Hall​ could you guide me some more on how to use GIT versioning with Data Mapper structures and maps?

[Anonymous]

Sorry for the delay in responding. I have been on holiday recently. Here are some guides on using Git with Talend.....

https://help.talend.com/r/en-US/8.0/software-dev-lifecycle-best-practices-guide/branching-merging-and-tagging

https://help.talend.com/r/en-US/8.0/best-practice-git-with-talend/git-feature-branch-workflow

https://help.talend.com/r/en-US/8.0/studio-user-guide-data-integration/reverting-project-item-on-tag