You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2017/01/04 09:14:58 UTC

[jira] [Updated] (ATLAS-1027) Atlas hooks should use properties from atlas-application.properties, instead of component's configuration

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

Madhan Neethiraj updated ATLAS-1027:
------------------------------------
    Fix Version/s: 0.7.1-incubating

Committed to 0.7-incubating branch: http://git-wip-us.apache.org/repos/asf/incubator-atlas/commit/785ee140eba79d46ef705a847075fc2e26e6eb54

> 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
>             Fix For: 0.8-incubating, 0.7.1-incubating
>
>         Attachments: ATLAS-1027.1.patch, 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)