Hi guys. I really like data profiling feature and would like to run it for views as well. As I see here it is hardcoded to run it only for tables. Can we have a separate config parameter(s) to specify which entity types(tables/views) to run profiling?

Currently we don’t profile views because it can be computation heavy. We can add it I think if there is need but i would not enable it by default.

This makes sense ^

I spent quite some time figuring out why our mart models hadn't been profiled. I thought that my allow/deny patterns were faulty. Only after sleeping over it I had the idea that these models being views could be causing it. So at least it was not the expected behaviour in my case. However, I do get the point that it might become expensive.

We have exactly the same use case, a presentation layer with a bunch of views with a filter on soft deleted records. It would be more convenient to see data profile right on a view than finding the corresponding original table for that view.