Bug: When viewing lineage from different entities

[Prajwal214]

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

Describe the bug
A clear and concise description of what the bug is.
-- Lineage from a Kafka topic is not displaying all upstream and downstream connections in the OpenMetadata. However, when clicking on the container in the same lineage view, it correctly shows two upstream connections to Pipeline.

To Reproduce

Screenshots or steps to reproduce

• Open lineage view for a Kafka topic.
• Observe that some upstream and downstream connections are missing.
• Click on the container in the same lineage.
• Notice that it correctly shows two upstream connections to Pipeline, which were missing when viewing from the Kafka topic.

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

• The Kafka topic lineage should show all correct upstream and downstream connections, just like when clicking on the container.
• No matter what entity your are viewing it should show the correct lineage and match

Incomplete lineage could lead to misinterpretation of data dependencies and impact data traceability for users.
Suggested Investigation:

Verify if lineage calculations are consistent across different entity types (Kafka topics vs. containers).
Check if missing connections are due to indexing delays, UI rendering issues, or incorrect metadata linking.

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.