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] [Commented] (ATLAS-542) Make qualifiedName and name consistent across all Datasets and Process
Date Tue, 14 Jun 2016 11:34:01 GMT

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

Hemanth Yamijala commented on ATLAS-542:
----------------------------------------

I just ran a few basic hive tests - via import and hook and see the names are coming as expected
with 'name' being short name and 'qualifiedName' is the complete name. Will commit this now,
and mark it as an incompatible change.

> Make qualifiedName and name consistent across all Datasets and Process
> ----------------------------------------------------------------------
>
>                 Key: ATLAS-542
>                 URL: https://issues.apache.org/jira/browse/ATLAS-542
>             Project: Atlas
>          Issue Type: Sub-task
>    Affects Versions: 0.7-incubating
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>             Fix For: 0.7-incubating
>
>         Attachments: ATLAS-542.1.patch, ATLAS-542.2.patch, ATLAS-542.3.patch, ATLAS-542.patch
>
>
> Currently hive_db, hive_column has qualifiedName holding the fully qualified Name and
name having the shorter name. 
> However hive_table has the fully qualified Name in "name" and shorter Name in tableName.
We should make this consistent for better search experience by removing tableName and keep
it consistent with db, column
> Same with hive_process, storm_topology, falcon_process - needs to have a qualifiedName




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

Mime
View raw message