If a mapping uses a view there is nothing that the mapping sees. So if you use the data catalog to scan said mappings we will scan and catalog the source but the actual mapping will not show anything. What will show the SQL behind the view is when you scan the database. When the catalog scans the underlying DB we will parse the SQL behind the view and present it in the UI.
Similiar if you use a SQL override in a mapping we will parse and connect the tables in the SQL back to source for complete lineage.
just to be sure)
from LineAge perspective, these approaches are equal
- SQL override with joins and filters (and so on )
- mapping with transformations
no. Lineage will look different in each of those case. While thy may end up with same sources and targets depending on how you define the map. The actual mapping tied to the lineage will be very different.