[ https://issues.apache.org/jira/browse/ATLAS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095712#comment-15095712 ]
Hemanth Yamijala edited comment on ATLAS-432 at 1/13/16 6:44 AM: ----------------------------------------------------------------- Attached patch incorporates the review comments from Shwetha. The method I've used to work with {{Referenceables}} instead of JSON objects is to use the API {{AtlasClient.getEntity}}. This required me to change the DB and View definitions to define name as a unique attribute. Thanks, [~shwethags] for the hint to use this method. Please review and let me know how this looks. was (Author: yhemanth): Attached patch incorporates the review comments from Shwetha. The method I've used to work with {{Referenceable}}s instead of JSON objects is to use the API {{AtlasClient.getEntity}}. This required me to change the DB and View definitions to define name as a unique attribute. Thanks, [~shwethags] for the hint to use this method. Please review and let me know how this looks. > 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, 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)