Forum Discussion
Resolver IIIFabric notebook when run via ADF pipeline trigger run issue
Thanks apturlov and BhaveshPatel for the inputs. The underlying issue was related to the DDL creation issue of one of the staging tables. However, as we used webactivity to invoke fabric notebooks, we could see some timeout issues, due to presence of parent and multiple child notebooks. We did increase the timeout in webactivity in ADF as well as in the child notebook call. This helped us to run the child notebooks completely and successfully. The ideal way will always be utilizing fabric pipelines and its notebooks so that the compute and connection strings remain in one environment to avoid the integreations issues. As webactivity coming out of ADF can have fabric notebook API call limitations which is be avoided in fabric.
Hope this helps other users who are working on the similar objectives.
Resolver IIIThanks apturlov and BhaveshPatel for the inputs. The underlying issue was related to the DDL creation issue of one of the staging tables. However, as we used webactivity to invoke fabric notebooks, we could see some timeout issues, due to presence of parent and multiple child notebooks. We did increase the timeout in webactivity in ADF as well as in the child notebook call. This helped us to run the child notebooks completely and successfully. The ideal way will always be utilizing fabric pipelines and its notebooks so that the compute and connection strings remain in one environment to avoid the integreations issues. As webactivity coming out of ADF can have fabric notebook API call limitations which is be avoided in fabric.
Hope this helps other users who are working on the similar objectives.
Hi ati_puri
It's great to hear that, and thank you for sharing the solution it will definitely be helpful for others facing the same issue. Please reach out to the community if you have any other questions; we're happy to assist you.