I am experimenting with CDDS based on the L3-DE course. I followed the instructions in the course by creating the Training subfolder and using Integrated Deployment to capture the transformation workflow. Afterwards I submitted it into the 01 - CDDS Development space.
If I understand the concept correctly, the captured transformation workflow should be generated under the Production subfolder automatically by CDDS in the 02 - CDDS Training space and the subsequent spaces (03 - CDDS Validation and 04 - CDDS Production space).
ah yes, sorry, now I wrapped my head around things (thank you @Lada for helping!). Could you try to set the Parameter Name in the Workflow Service Output Node of your Training Workflow to prediction-workflow?
I tried to run the example mentioned in the link you posted (Level_2_Fraud Detection with ID) and it created the Production subfolder successfully. I’m wondering whether the captured workflow segment has to contain ML related nodes or can it be a normal ETL workflow? (in my workflow, I am NOT using any ML related node (e.g. Partitioning, Learner, Predictor, etc.)
So I assume, it has something to do with the Validation subfolder. I tried to run the unit test workflow under the Validation subfolder and it was executed successfully in Business Hub
Is it something I overlooked with regards to the Validation subfolder or its underlying Unit Test workflow? or is it not allowed to have the Validation subfolder at all?
ok, one step closer with the correct parameter name
So long the training workflow contains the integrated deployment nodes and the Workflow Service Output at the end (with the parameter name now correctly set), it does not matter which kind of nodes are used in the rest of the workflow. A normal ETL workflow will work just fine.
We are still investigating—the current working hypothesis is that the production workflow wasn’t copied in time to the location where the custom test can access it.
hmm, the issue is still elusive: I used your example as a base for my experiment, and copied a folder Lukas test 1 (which contains the same data, Training, and Validation folder as you used in your project CDDS Workflow with validation hanantoprabowo) to 02 CDDS - Training > Queue.
After a little while (2 minutes or so) I see the folder structure including a Production folder in 03 CDDS - Validation > Pending.
What I did in the past was I published the artifact into 01 CDDS - Development folder as mentioned in the L3 course. I did the same few minutes ago and still experienced the same issue.
I tried to publish it to 02 CDDS - Training > Queue folder as mentioned in your post, but I received an error message: The selected folder is not writable. Choose a new location.
I’m wondering:
which folder the artifact has to be published into? 01 - CDDS Development or 02 CDDS - Training > Queue?
In case of 02 CDDS - Training > Queue, maybe I’m lacking of permission to be able to write into the folder?
we found something on our end, and we identified an issue with the User Data App, where your project is pushed directly to Validation, skipping the Training step, if there is the Validation folder in your project—thus not creating the Production folder. Nothing wrong on your end I’ll see to fix it and will come back to you!
first of all sorry for the late reply! There was some sickness in the way, and the issue seems to be somewhat larger than anticipated:
the skipping part is solved, and the Production subfolder should now be created
however, the Validation workflow fails due to a technical reason: the trigger that validates fires before all data the test-workflow requires is copied over, leading it to fail. We are still working on finding a reasonable fix for this one.
I apologize again (and will offer a call via PN )!
)!