Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lineage display problem with custom connector #19168

Open
hmtgn opened this issue Dec 23, 2024 · 0 comments
Open

Lineage display problem with custom connector #19168

hmtgn opened this issue Dec 23, 2024 · 0 comments

Comments

@hmtgn
Copy link

hmtgn commented Dec 23, 2024

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
image
image
The pipeline is a custom connector created via API with this code:

create_pipeline = CreatePipelineRequest(
            name=pipeline_name,
            service=pipeline_service.fullyQualifiedName,
            description=description
        )
pipeline_entity = metadata.create_or_update(data=create_pipeline)

source_table_ref = EntityReference(id=source_table.id, type="table")
pipeline_ref = EntityReference(id=pipeline_entity.id, type="pipeline")

lineage_request_source_to_pipeline = AddLineageRequest(
            edge=EntitiesEdge(fromEntity=source_table_ref, toEntity=pipeline_ref)
        )
metadata.add_lineage(data=lineage_request_source_to_pipeline)

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:

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

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant