atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ATLAS-242) The qualified name for hive entities should be backward compatible
Date Mon, 07 Dec 2015 08:44:10 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15044574#comment-15044574
] 

Shwetha G S edited comment on ATLAS-242 at 12/7/15 8:43 AM:
------------------------------------------------------------

Committed to master and branch-0.6-incubating. Thanks Suma for reviewing


was (Author: shwethags):
Committed to master. Thanks Suma for reviewing

> The qualified name for hive entities should be backward compatible
> ------------------------------------------------------------------
>
>                 Key: ATLAS-242
>                 URL: https://issues.apache.org/jira/browse/ATLAS-242
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: David Kaspar
>            Assignee: Shwetha G S
>             Fix For: trunk
>
>         Attachments: ATLAS-242-v2.patch, ATLAS-242.patch
>
>
> This issue is filed for "RangerAtlasDemo_v4.ova" VM-image release.
> When I call:
> http://127.0.0.1:21000/api/atlas/lineage/hive/table/{tableName}/schema
> REST API method, then it always returns 404 Not Found and returns an error which claims
that given {tableName} does not exist.
> Since REST API documentation (application.wadl) does not state details, I have tried
to use existing Hive table names, existing GUIDs of Hive tables but none of them works.
> Similarly for /api/atlas/lineage/hive/table/{tableName}/outputs/graph and /api/atlas/lineage/hive/table/{tableName}/inputs/graph.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message