Skip to content

Fix: Pipeline Lineage Search and Backend exceptions (#27254) #27271

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.

Sign up for GitHub

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

Open
aniruddhaadak80 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Fix: Pipeline Lineage Search and Backend exceptions (#27254) #27271

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1eeedc0
Fix pipeline lineage dropping in backend and UI
aniruddhaadak80 Apr 11, 2026
03756fc
test: add test for AddPipeLineModal
aniruddhaadak80 Apr 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 16 additions & 14 deletions openmetadata-service/src/main/java/org/openmetadata/service/jdbi3/LineageRepository.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -452,22 +452,24 @@ public static void addPipelineDetails(EsLineageData lineageData, EntityReference
if (nullOrEmpty(pipelineRef)) {
lineageData.setPipeline(null);
} else {
Pair<String, Map<String, Object>> pipelineOrStoredProcedure =
getPipelineOrStoredProcedure(
pipelineRef, List.of("changeDescription", "incrementalChangeDescription"));
lineageData.setPipelineEntityType(pipelineOrStoredProcedure.getLeft());
lineageData.setPipeline(pipelineOrStoredProcedure.getRight());
try {
Pair<String, Map<String, Object>> pipelineOrStoredProcedure =
getPipelineOrStoredProcedure(
pipelineRef, List.of("changeDescription", "incrementalChangeDescription"));
lineageData.setPipelineEntityType(pipelineOrStoredProcedure.getLeft());
lineageData.setPipeline(pipelineOrStoredProcedure.getRight());
} catch (Exception ex) {
LOG.warn("Failed to get pipeline details for elastic search mapping", ex);
lineageData.setPipelineEntityType(pipelineRef.getType());
lineageData.setPipeline(JsonUtils.getMap(pipelineRef));
}
}
}
}

public static Pair<String, Map<String, Object>> getPipelineOrStoredProcedure(
EntityReference pipelineRef, List<String> fieldsToRemove) {
Map<String, Object> pipelineMap;
if (pipelineRef.getType().equals(PIPELINE)) {
pipelineMap =
JsonUtils.getMap(
Entity.getEntity(pipelineRef, "pipelineStatus,tags,owners", Include.ALL));
} else {
public static Pair<String, Map<String, Object>> getPipelineOrStoredProcedure(
EntityReference pipelineRef, List<String> fieldsToRemove) {
Map<String, Object> pipelineMap;
if (pipelineRef.getType().equalsIgnoreCase(Entity.PIPELINE)) {
pipelineMap = JsonUtils.getMap(Entity.getEntity(pipelineRef, "tags,owners", Include.ALL));
}

Expand Down
Binary file modified ...sources/ui/src/components/Entity/EntityLineage/AppPipelineModel/AddPipeLineModal.test.tsx
View file
Open in desktop
Binary file not shown.
11 changes: 6 additions & 5 deletions ...in/resources/ui/src/components/Entity/EntityLineage/AppPipelineModel/AddPipeLineModal.tsx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,12 +75,13 @@ const AddPipeLineModal = ({
pageSize: PAGE_SIZE,
searchIndex: [SearchIndex.PIPELINE, SearchIndex.STORED_PROCEDURE],
});
const edgeOptions = data.hits.hits.map((hit) =>
getEntityReferenceFromEntity(
const edgeOptions = data.hits.hits.map((hit) => {
const entityType = hit._source.entityType || (hit._index.includes('pipeline') ? EntityType.PIPELINE : EntityType.STORED_PROCEDURE);
Copy link
Copy Markdown

@gitar-bot gitar-bot bot Apr 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Edge Case: Pipeline type fallback relies on fragile index name check

When hit._source.entityType is missing, the fallback hit._index.includes('pipeline') depends on the Elasticsearch/OpenSearch index naming convention. If the index name changes (e.g., versioned indices like pipeline_search_index_v2, or aliased differently), this heuristic could misclassify entities. This is a reasonable workaround for the immediate bug, but is fragile for long-term maintenance.

Was this helpful? React with 👍 / 👎 | Reply gitar fix to apply this suggestion

return getEntityReferenceFromEntity(
hit._source,
hit._source.entityType as EntityType
)
);
entityType as EntityType
);
});

setEdgeOptions(edgeOptions);
} catch (error) {
Expand Down
Loading