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

Tiffany Nguyen updated ATLAS-2779:
----------------------------------
    Description: 
Create Hive Metastore Event listener to push table changes to Atlas. This will 
help push changes done via SparkSQL which does not go through hivehook to 
reflect in Atlas.
Furthermore, this will eliminate the need to set hook on the client side to 
capture DDL. For example, using hive CLI (by typing hive at command line) would 
require changes in hive-site.xml on the client side to include hook property 
(hive.exec.post.hooks). The benefit of no change needed on client side is 
amplified in environment where there are hundreds of clients.

  was:Create Hive Metastore Event listener to push table changes to Atlas. This 
will help push changes done via SparkSQL which does not go through hivehook to 
reflect in Atlas. 


> Create Hive Metastore Event listener to push table changes to Atlas.
> --------------------------------------------------------------------
>
>                 Key: ATLAS-2779
>                 URL: https://issues.apache.org/jira/browse/ATLAS-2779
>             Project: Atlas
>          Issue Type: Improvement
>          Components:  atlas-core
>    Affects Versions: 1.0.0-alpha
>            Reporter: Tiffany Nguyen
>            Priority: Major
>             Fix For: 1.0.0-alpha
>
>
> Create Hive Metastore Event listener to push table changes to Atlas. This 
> will help push changes done via SparkSQL which does not go through hivehook 
> to reflect in Atlas.
> Furthermore, this will eliminate the need to set hook on the client side to 
> capture DDL. For example, using hive CLI (by typing hive at command line) 
> would require changes in hive-site.xml on the client side to include hook 
> property (hive.exec.post.hooks). The benefit of no change needed on client 
> side is amplified in environment where there are hundreds of clients.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to