ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taeyun Kim (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-9255) Show why Configs Save button is disabled
Date Thu, 22 Jan 2015 08:10:34 GMT

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

Taeyun Kim updated AMBARI-9255:
-------------------------------
    Description: 
After YARN Configs is changed and saved, there is a case that the saved configuration itself
bacomes invalid state(for example, some config value is missing).

In my case, the missing one was 'yarn.resourcemanager.fs.state-store.uri'. But that variable
is hidden in the folded 'Advanced yarn-site' group, so there is no clue that some variable
has incorrect or missing value.

So when I change an another config value, Discard button is enabled, but Save button is not
enabled. But I see no clue why.

Here, there are 2 problems:

1. Incorrect state is saved by UI. It should not happen.
2. Sometimes it's hard to see what is wrong that's preventing Save.

So, at least for the 2nd problem, it would be nice to show what is wrong.

  was:
After YARN Configs is changed and saved, there is a case that the saved configuration itself
bacomes invalid state(for example, some config value is missing).

In my case, the missing one was 'yarn.resourcemanager.fs.state-store.uri'. But that variable
is hidden in the folded 'Advanced yarn-site' group, so there is no clue that some variable
has incorrect or missing value.

So when I change an another config value, Discard button is enabled, but Save button is not
enabled. But I see no clue why.

Here, there are 2 problems:

1. Incorrect state is saved by UI. It should not happen.
2. Soometimes it's hard to see what is wrong that's preventing Save.


> Show why Configs Save button is disabled
> ----------------------------------------
>
>                 Key: AMBARI-9255
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9255
>             Project: Ambari
>          Issue Type: Improvement
>    Affects Versions: 1.7.0
>            Reporter: Taeyun Kim
>            Priority: Minor
>
> After YARN Configs is changed and saved, there is a case that the saved configuration
itself bacomes invalid state(for example, some config value is missing).
> In my case, the missing one was 'yarn.resourcemanager.fs.state-store.uri'. But that variable
is hidden in the folded 'Advanced yarn-site' group, so there is no clue that some variable
has incorrect or missing value.
> So when I change an another config value, Discard button is enabled, but Save button
is not enabled. But I see no clue why.
> Here, there are 2 problems:
> 1. Incorrect state is saved by UI. It should not happen.
> 2. Sometimes it's hard to see what is wrong that's preventing Save.
> So, at least for the 2nd problem, it would be nice to show what is wrong.



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

Mime
View raw message