Better tracking of non populated datasetsAnswered
Today, the "dataset not populated" error in the execution log seems to be inherited to all connected pipes. However, the name of the pipe with the initial unpopulated dataset is not.
I.e. let's say pipe A is actually unpopulated. Pipe B uses Pipe A as a source dataset. Pipe C does a hops to pipe B. In the execution log to pipe C it will say that the dataset to pipe B is unpopulated, which is not very helpful. I also believe that if pipe D does a hops to dataset C, it will get the error message that dataset C is unpopulated (the dataset C could even have output if they ran the pipe before adding the hops to dataset C).
It would be nice if we could actually see which dataset/datasets are actually unpopulated, and not just the last dataset in the communicaiton line.
The "Graph" tab on a pipe will let you see what related datasets are unpopulated. You could then traverse the graph upwards or side-ways to identify the dataset(s) that cause the lack of propagation of the populated flag.Comment actions
Please sign in to leave a comment.