ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Onischuk (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-6844) Falcon-oozie configuration issues
Date Wed, 13 Aug 2014 14:46:12 GMT

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

Andrew Onischuk resolved AMBARI-6844.
-------------------------------------

    Resolution: Fixed

Committed to trunk

> Falcon-oozie configuration issues
> ---------------------------------
>
>                 Key: AMBARI-6844
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6844
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 1.8.0
>
>
> PROBLEM #1:
> After we add new property to oozie-site.xml, like:
> oozie.service.ELService.ext.functions.coord-action-create. This property will
> show in falcon config, but it cannot be updated. It's read-only.
> PROBLEM #2:
> Every time, when we modify the oozie-site.xml, Ambari will suggest to restart
> both oozie and falcon, even the property is not related to Falcon. As I
> undertand, modify oozie-site.xml, falcon doesn't need to be restarted.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message