Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Have a question I'm hoping someone could get me pointed in the right direction. I've got a single Talend package that we pass in different queries and configuration options to out of a table depending on a client id that is passed in. There are multiple TAC jobs that run that same package snapshot with the client id indicated in a context. Currently we have about 125 clients, therefore we have about 125 TAC jobs running a different times during the month. That all works fine. The issue comes when we need to deploy a new snapshot. When that occurs, every TAC job then needs to be updated, presumably manually, to assign it to the new snapshot version.
One idea that we had, was to create execution plans instead of a TAC job and each execution plan is then tied to a single TAC job. That would allow us to change the snapshot on the single TAC job and every execution plan would inherit those changes.
Does anyone see any potential issues with the execution plan approach or perhaps have another idea that we could look into?
Thanks in advance.
z
There is an option for normal tasks and for artifact tasks to 'use latest version' moving forward with this option will ensure when changes occur to the job and those changes are pushed to git or an artifact repository then the underlying task in tac will be updated automatically when the task is executed.
https://help.talend.com/r/RK~CAb9nJ1erxR8SrBbKoQ/65So~Pr5yMhtDa6zGao56A
I believe you can use the metaservlet command to update all tasks to have this option but would refrain from ever making any changes to the backend database.