atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1027) Atlas hooks should use properties from atlas-application.properties, instead of component's configuration
Date Mon, 18 Jul 2016 19:46:20 GMT

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

Suma Shivaprasad commented on ATLAS-1027:
-----------------------------------------

Tests are failing in HiveHookIT with the patch . Will need to be fixed before committing.

> Atlas hooks should use properties from atlas-application.properties, instead of component's
configuration
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ATLAS-1027
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1027
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Madhan Neethiraj
>            Assignee: Madhan Neethiraj
>         Attachments: ATLAS-1027.patch
>
>
> Currently Atlas hook for Hive/Storm/Sqoop read properties from component's configuration
and atlas-application.properties. Having the hooks read the properties only from atlas-application.properties
would make it easier to manage. Only updates to component's configuration should be to register
Atlas hook with the component. The hook implementation should only read necessary run time
configuration from its own config file - atlas-application.propertiees.



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

Mime
View raw message