Description
Add a generic mechanism for recording the fact that one object depends on another. First use case (to be implemented as part of this task) would be views depending on tables or other views, but in the future we can also use this for views depending on persistent functions, functions depending on other functions, etc.
This involves metastore modeling, QL analysis for deriving and recording the dependencies (Ashish says something may already be available from the lineage work), and CLI support for browsing dependencies.