Debugging/Versioning Applications as a Recipe
Hi,
I am looking into packaging a part of a flow as a recipe to be used across multiple projects (https://doc.dataiku.com/dss/latest/applications/application-as-recipe.html#sharing-an-application-as-recipe). I have a couple of questions:
1. It appears that any changes made in the original project get transmitted to all projects where the recipe is used. Is it possible to create versions and tracking them?
2. Suppose the application-as-a-recipe fails. The error message returned is fairly unhelpful (see attached). This failure happened due to a division by 0 error in a Python recipe. What is the easiest way to debug an application-as-a-recipe when there are failures? (Preferably, this does not involve running the original flow with the inputs that triggers errors).
Answers
-
yashpuranik Partner, Dataiku DSS Core Designer, Dataiku DSS ML Practitioner, Neuron, Dataiku DSS Adv Designer, Registered, Neuron 2022, Neuron 2023 Posts: 69 NeuronOptions
As a follow up, checking keep instance (https://community.dataiku.com/t5/Using-Dataiku/Applications-as-recipes-and-logging/m-p/14441) works for debugging. It creates new projects in a folder called App Instances and names start with Execute
-
CoreyS Dataiker Alumni, Dataiku DSS Core Designer, Dataiku DSS Core Concepts, Registered Posts: 1,150 ✭✭✭✭✭✭✭✭✭OptionsThank you for sharing how you found the solution with the rest of the community @yashpuranik
!