You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Srimanth Gunturi (JIRA)" <ji...@apache.org> on 2014/04/16 19:42:16 UTC
[jira] [Reopened] (AMBARI-5478) Flume configurations should not
have 'flume-conf' type
[ https://issues.apache.org/jira/browse/AMBARI-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srimanth Gunturi reopened AMBARI-5478:
--------------------------------------
Apologies for this, but it turns out backend is looking for "flume-conf" instead of "flume-agent". We need to save configs to {{configurations?type=flume-conf}}.
> Flume configurations should not have 'flume-conf' type
> ------------------------------------------------------
>
> Key: AMBARI-5478
> URL: https://issues.apache.org/jira/browse/AMBARI-5478
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.6.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Fix For: 1.6.0
>
>
> When I installed Flume service I saw 2 (flume-agent and flume.conf) configurations instead of 1. The API also has {{configurations?type=flume-agent&tag=version1}} and {{configurations?type=flume-conf&tag=version1}}.
> We should only have {{flume-agent}} config. The section title should be "flume-agent.conf" and the text area will have default value of "# Flume agents configuration". When saved the changes should be persisted in "content" key of {{type=flume-agent}}.
--
This message was sent by Atlassian JIRA
(v6.2#6252)