You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected module
Does it impact the UI, backend or Ingestion Framework?
UI Describe the bug
A clear and concise description of what the bug is.
I have a problem displaying the lineage with a custom connector (I can see that there is a lineage but I can't display it even with the “+”).
This is a display bug concerning the reference point from which the lineage is displayed (as you can see on the screenshots below).
To Reproduce
Screenshots or steps to reproduce
The pipeline is a custom connector created via API with this code:
Expected behavior
A clear and concise description of what you expected to happen.
To be able to display the lineage of the custom pipeline depousi the pipeline in question without needing to find a table linking upstream or downstream.
Affected module
Does it impact the UI, backend or Ingestion Framework?
UI
Describe the bug
A clear and concise description of what the bug is.
I have a problem displaying the lineage with a custom connector (I can see that there is a lineage but I can't display it even with the “+”).
This is a display bug concerning the reference point from which the lineage is displayed (as you can see on the screenshots below).
To Reproduce
Screenshots or steps to reproduce
The pipeline is a custom connector created via API with this code:
Expected behavior
A clear and concise description of what you expected to happen.
To be able to display the lineage of the custom pipeline depousi the pipeline in question without needing to find a table linking upstream or downstream.
Version:
openmetadata-ingestion[docker]==XYZ
] 1.5.12.1Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: