Because recently i tried to implement, a job which falls in a Infinite Cyclic Call , there i got to know that it doesent validate via DAG, principle...
And the Jobs Runs Infinitely....
So , My Question is What is the Design Motive behind Matillion ?
Is it a DAG ! Usually it is ...
If yes, then i think user must, ensure it doesnt falls in a infinite loop...
Matillion is DAG but I don't think I agree with your assertation that it means it should/could stop a user from creating an infinite loop. I would assert that if you've created an infinite loop that's a bigger red flag that your approach to your job designed is flawed. You should redesign your job so it can have a definitive start and end to the execution. It's okay to queue up another execution at the completion of an execution but each execution should be independent and be able to end.
I would agree with @MichaelBlack but I can see where there is some confusion. In a traditional DAG based system like Apache Airflow, it will not allow you to create the cyclical infinite loop. It's simply not possible. Matillion on the other hand will allow you depending on the situation. So, the answer is that Matillion does loosely follow DAG. I would say the validation follows 95% to 98% of true DAG.
The good and the bad of Matillion is that it's extremely flexible. You can do almost anything you want but it also allows you to get yourself in to predicaments due to it's flexibility.
Actually, i was thinking from airflow perspective as mentioned by @Bryan so, thought of why not matillion is not enforcing such rules.
But anyways, i got a clear understanding from both of your answers, i.e we as user needs to meticulously design the jobs, by avoiding a cyclic loop.