[
https://issues.apache.org/jira/browse/ATLAS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065674#comment-15065674
]
Hemanth Yamijala commented on ATLAS-405:
----------------------------------------
Tested the patch. It is working fine functionally. I even tested with an
extended topology that is like this:
[DataSet 1] -> (3 processes) -> [DataSet 2] -> (1 process) -> [DataSet 3]
|
| -> (1 process) ->
[DataSet 4]
This is working fine as well. However, the view is a bit spoilt. The image
scrolls off to the extreme right, and shows up empty initially. The user needs
to scroll to bring it into view, and even then, the edges are all very
stretched and long. Basically the picture doesn't fit into one view easily.
Will upload a screen shot - can you please take a look?
> UI: Lineage is broken seemingly if there are more than one input Processes
> creating a Dataset
> ---------------------------------------------------------------------------------------------
>
> Key: ATLAS-405
> URL: https://issues.apache.org/jira/browse/ATLAS-405
> Project: Atlas
> Issue Type: Bug
> Reporter: Hemanth Yamijala
> Assignee: Darshan Kumar
> Priority: Blocker
> Labels: patch-available
> Attachments: ATLAS-405.patch, failing_lineage.png,
> failing_lineage_api_responses.txt, failing_lineage_entity_responses.txt,
> spikedMockData.png, working_lineage.png, working_lineage_api_responses.txt
>
>
> I have a slightly complex lineage which is like this:
> [DataSet 1] -> (3 processes) -> [DataSet 2] -> (1 process) -> [DataSet 3]
> When I click on DataSet1, the lineage graph is showing correctly.
> When I click on DataSet2, the lineage graph is broken. What is happening is
> that there are 2 dangling processes on the input side of DataSet 2 which are
> not linked to the DataSet 1. Only one of the processes seems linked. It
> appears that maybe the graph walking is not taking into effect multiple
> inputs to a vertex like DataSet 2.
> The API response is right. I will upload images of working and failing
> lineages with the corresponding responses in follow-up comments.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
