ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Fernandez (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-17183) client.properties for Falcon should be configurable via Ambari
Date Thu, 23 Jun 2016 18:22:16 GMT

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

Alejandro Fernandez resolved AMBARI-17183.
------------------------------------------
    Resolution: Fixed

Pushed to trunk, commit 4a3fb6ef1db5ef15c0caca958a7a72786b0fafd3
branch-2.4, commit 16d63dabf41f2dcb58a51d537ec9262e7f4a4f79

> client.properties for Falcon should be configurable via Ambari
> --------------------------------------------------------------
>
>                 Key: AMBARI-17183
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17183
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.2.0
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17183-2.patch, AMBARI-17183.patch.2
>
>
> Everytime Falcon is restarted using Ambari, the client.properties under /usr/hdp/current/falcon-client/conf/client.properties
gets overwritten by default properties. But there are scenarios where a Falcon user might
wish to change the falcon.url in client.properties, or add custom client.properties.
> Ambari should provide a way to do this.



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

Mime
View raw message