Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Job dependency at project level

Hi Team,

I am using Talend data fabric 6.4.1. In our project we have around 180+ jobs. All jobs are running fine in prod. Now we need to add some additional fields to existing jobs. I have a concern that how can i identify job dependency at project level, for example, if i have added some fields to one job, the same fields we are going to add in DB so the same table will be used by some other jobs then all jobs may get into trouble (My assumption correct me if i am wrong ). That's why i need an intelligent way to identify how to check job dependency at project level.

 

I have tried most of the ways,

             1. By using the Impact analysis (We are using Builtin load by using config file to read details so it is not useful )

             2. In workspace .items file (File is empty for me because we are connecting from central repository by using remote connection)

 

Could you please let me know is there any alternative and intelligent way to identify job dependency at project level with quite accurately and if any documentation is available please share in this forum.

 

Any help is much appreciated and helpful for us !!

 

Regards,

MS

Labels (2)
2 Replies
Anonymous
Not applicable
Author

Hi, 

 

    For data lineage and forward impact analysis, Talend has already Talend Data Catalog tool which will help you in enterprise level Data Governance.

 

    I would suggest to talk to your Customer Success Manager since you are already an Enterprise customer and they can help you do to necessary demos and detailed walkthrough of the product. Another good thing with Talend Data Catalog is that it integrates seamlessly with Talend Studio jobs.

 

Warm Regards,
Nikhil Thampi

Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂

Anonymous
Not applicable
Author

A good way of preventing this sort of problem is to always use repository schemas. If you use a repository schema and it is changed, the update will trigger other jobs using it to be changed. You will see which jobs in your Studio. 

 

Another way of tracking this is to scan the .items files from the workspace. If you do this you should ensure that you are working on a copy of those files. However you say "File is empty for me because we are connecting from central repository by using remote connection". I do not understand this I am afraid. You will always have a local copy of these files when working with the Studio. Can you explain what you mean by this?