[
https://issues.apache.org/jira/browse/ATLAS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092249#comment-15092249
]
Hemanth Yamijala commented on ATLAS-432:
----------------------------------------
The issue was occurring due to changes in ATLAS-342, where the APIs started
returning all IDs added/updated as part of an entity creation call. Due to
this, {{QuickStart.createInstance}}, which was assuming that the first ID in
the returned list was the ID of the newly created entity was broken. As a
result, the lineage added using this ID was not showing up correctly.
> QuickStart lineage is broken
> ----------------------------
>
> Key: ATLAS-432
> URL: https://issues.apache.org/jira/browse/ATLAS-432
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 0.6-incubating
> Reporter: Hemanth Yamijala
> Assignee: Hemanth Yamijala
> Attachments: ATLAS-432.patch
>
>
> * Run quick_start.py on the release version of 0.6.
> * Query for Table, select sales_fact table from the results
> * You will not see any lineage graph even though QuickStart adds a
> LoadProcess that captures information for the lineage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
