atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ATLAS-432) QuickStart lineage is broken
Date Mon, 11 Jan 2016 16:41:39 GMT

     [ https://issues.apache.org/jira/browse/ATLAS-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hemanth Yamijala updated ATLAS-432:
-----------------------------------
    Attachment: ATLAS-432.patch

The fix for the issue was to ensure we pick the last entity ID in the return from the API
as that would be the ID of the created entity.

In addition to the fix, I also added a set of integration tests for QuickStart that test that
the various main elements of QuickStart are added properly. To make this test work, I need
to change a few things in the existing ITs, notably with respect to making sure the same types
added by QuickStart are not being added again, as all these are run together against the same
instance of the Atlas server.

> 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)

Mime
View raw message