Lineage Graph Behavior for Derived Column Dependencies

[Prajwal214]

Affected module
Does it impact the UI, backend or Ingestion Framework?
--- Ingestion

Describe the bug
A clear and concise description of what the bug is.
-- I have a column IS_EMAILABLE which is defined - it depends on EMAILABLE in the upstream table CARDHOLDER_ACTIVE_VW as well as a field HAS_UNSUBSCRIBED which is defined within the same SELECT statement and depends on upstream tables CARDHOLDER_ACTIVE_VW, CARD_COMM_TYPE_OPT_OUT and DIM_COMM_TYPE. However, in the lineage graph it is showing as just coming directly off CARDHOLDER_ACTIVE_VW , as in the second screengrab. Would we expect it to be able to figure out the other two upstream tables?

To Reproduce

Screenshots or steps to reproduce

Expected behavior
A clear and concise description of what you expected to happen.

Version:

• OS: [e.g. iOS]
• Python version:
• OpenMetadata version: [e.g. 0.8]
• OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]

Additional context
Add any other context about the problem here.