[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven
[ https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876407#comment-14876407 ] Mahadev konar commented on AMBARI-13069: +1 on the patch for backport to 2.1. > Attributes of configuration property should be stack API driven > --- > > Key: AMBARI-13069 > URL: https://issues.apache.org/jira/browse/AMBARI-13069 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web, stacks >Affects Versions: 2.1.3 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.1.3 > > Attachments: AMBARI-13069.patch, AMBARI-13069_2.patch, > AMBARI-13069_3.patch, AMBARI-13069_4.patch, AMBARI-13069_branch-2.1.3.patch > > > *Following attributes of configuration properties should be made stack API > driven:* > # Visibility of configuration property > # display name of configuration property > # Empty value validity of configuration property > # Restriction of being configured only once on installation > # overridable in config host group > # Name of the property should be hidden > # Unit of the property > *Achieving this task will be useful in following scenarios:* > # custom services could be added with less changes in ambari-web code > # Any issues related to configuration property attributes encountered on a > deployed cluster can be addressed by making stack changes rather than > redeploying ambari-web code with a fix. For example if a property tagged as > not overridable if later desired to be made overridable on a deployed cluster > will now require changing a boolean flag in stack configuration property > rather than changing ambari-web code. > # Config property only in a specific stack can be attributed without writing > stack specific logic in ambari-web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven
[ https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876664#comment-14876664 ] Hudson commented on AMBARI-13069: - SUCCESS: Integrated in Ambari-branch-2.1 #557 (See [https://builds.apache.org/job/Ambari-branch-2.1/557/]) AMBARI-13069. Attributes of configuration property should be stack API driven. (jaimin) (jaimin: http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=35ac6fbfc0c3eb922c1f9bed1d2fcd4810e4cbe2) * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/HBASE/configuration/hbase-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/FLUME/configuration/flume-conf.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/STORM/configuration/storm-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/YARN/configuration-mapred/mapred-env.xml * ambari-server/src/main/resources/stacks/HDP/2.1/services/PIG/configuration/pig-properties.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-env.xml * ambari-web/test/data/HDP2/site_properties_test.js * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-env.xml * ambari-server/src/main/resources/common-services/HBASE/0.96.0.2.0/configuration/hbase-site.xml * ambari-server/src/main/java/org/apache/ambari/server/controller/internal/StackLevelConfigurationResourceProvider.java * ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hdfs-site.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-log4j.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/AMBARI_METRICS/configuration/ams-site.xml * ambari-web/app/data/HDP2.2/site_properties.js * ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/ranger-yarn-plugin-properties.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/TEZ/configuration/tez-site.xml * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/ranger-knox-plugin-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/configuration/ranger-kafka-audit.xml * ambari-server/src/main/resources/common-services/RANGER_KMS/0.5.0.2.3/configuration/kms-log4j.xml * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/knox-env.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/STORM/configuration/storm-site.xml * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * ambari-server/src/main/resources/common-services/PIG/0.12.0.2.0/configuration/pig-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/core-site.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-env.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-env.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HDFS/configuration/hadoop-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/OOZIE/configuration/oozie-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HBASE/configuration/hbase-env.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/webhcat-site.xml * ambari-server/src/main/resources/common-services/ACCUMULO/1.6.1.2.2.0/configuration/accumulo-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/ZOOKEEPER/configuration/zookeeper-env.xml * ambari-server/src/main/resources/common-services/KAFKA/0.8.1.2.2/configuration/kafka-log4j.xml * ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/topology.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/HBASE/configuration/hbase-site.xml * ambari-server/src/main/resources/common-services/ZOOKEEPER/3.4.5.2.0/configuration/zookeeper-env.xml * ambari-server/src/main/resources/stacks/HDP/2.1/services/OOZIE/configuration/oozie-site.xml * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-log4j.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/KNOX/configuration/ranger-knox-audit.xml * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/gateway-log4j.xml * ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/configuration/spark-defaults.xml *
[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven
[
https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741358#comment-14741358
]
Hadoop QA commented on AMBARI-13069:
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12755421/AMBARI-13069.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3771//console
This message is automatically generated.
> Attributes of configuration property should be stack API driven
> ---
>
> Key: AMBARI-13069
> URL: https://issues.apache.org/jira/browse/AMBARI-13069
> Project: Ambari
> Issue Type: Task
> Components: ambari-server, ambari-web, stacks
>Affects Versions: 2.2.0
>Reporter: Jaimin D Jetly
>Assignee: Jaimin D Jetly
> Fix For: 2.2.0
>
> Attachments: AMBARI-13069.patch
>
>
> *Following attributes of configuration properties should be made stack API
> driven:*
> # Visibility of configuration property
> # display name of configuration property
> # Empty value validity of configuration property
> # Restriction of being configured only once on installation
> # overridable in config host group
> # Name of the property should be hidden
> *Achieving this task will be useful in following scenarios:*
> # custom services could be added with less changes in ambari-web code
> # Any issues related to configuration property attributes encountered on a
> deployed cluster can be addressed by making stack changes rather than
> redeploying ambari-web code with a fix. For example if a property tagged as
> not overridable if later desired to be made overridable on a deployed cluster
> will now require changing a boolean flag in stack configuration property
> rather than changing ambari-web code.
> # Config property only in a specific stack can be attributed without writing
> stack specific logic in ambari-web
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven
[ https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741802#comment-14741802 ] Jaimin D Jetly commented on AMBARI-13069: - Attached [^AMBARI-13069_4.patch] with additional fixes. > Attributes of configuration property should be stack API driven > --- > > Key: AMBARI-13069 > URL: https://issues.apache.org/jira/browse/AMBARI-13069 > Project: Ambari > Issue Type: Task > Components: ambari-server, ambari-web, stacks >Affects Versions: 2.2.0 >Reporter: Jaimin D Jetly >Assignee: Jaimin D Jetly > Fix For: 2.2.0 > > Attachments: AMBARI-13069.patch, AMBARI-13069_2.patch, > AMBARI-13069_3.patch, AMBARI-13069_4.patch > > > *Following attributes of configuration properties should be made stack API > driven:* > # Visibility of configuration property > # display name of configuration property > # Empty value validity of configuration property > # Restriction of being configured only once on installation > # overridable in config host group > # Name of the property should be hidden > *Achieving this task will be useful in following scenarios:* > # custom services could be added with less changes in ambari-web code > # Any issues related to configuration property attributes encountered on a > deployed cluster can be addressed by making stack changes rather than > redeploying ambari-web code with a fix. For example if a property tagged as > not overridable if later desired to be made overridable on a deployed cluster > will now require changing a boolean flag in stack configuration property > rather than changing ambari-web code. > # Config property only in a specific stack can be attributed without writing > stack specific logic in ambari-web -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AMBARI-13069) Attributes of configuration property should be stack API driven
[ https://issues.apache.org/jira/browse/AMBARI-13069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14741874#comment-14741874 ] Hudson commented on AMBARI-13069: - SUCCESS: Integrated in Ambari-trunk-Commit #3432 (See [https://builds.apache.org/job/Ambari-trunk-Commit/3432/]) AMBARI-13069. Attributes of configuration property should be stack API driven. (jaimin) (jaimin: http://git-wip-us.apache.org/repos/asf?p=ambari.git=commit=70ca85005b49a93970164af9a047bebd2b290427) * ambari-server/src/main/resources/common-services/RANGER/0.4.0/configuration/usersync-properties.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/TEZ/configuration/tez-site.xml * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/topology.xml * ambari-server/src/main/resources/common-services/SPARK/1.2.0.2.2/configuration/spark-log4j-properties.xml * ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/configuration/ams-site.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/YARN/configuration/ranger-yarn-plugin-properties.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hdfs-site.xml * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/webhcat-log4j.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/OOZIE/configuration/oozie-site.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/core-site.xml * ambari-server/src/main/resources/stacks/HDP/2.1/services/YARN/configuration/yarn-env.xml * ambari-server/src/main/java/org/apache/ambari/server/state/ValueAttributesInfo.java * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/FLUME/configuration/flume-conf.xml * ambari-server/src/main/resources/common-services/FLUME/1.4.0.2.0/configuration/flume-conf.xml * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/gateway-log4j.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.2/services/HBASE/configuration/hbase-env.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-site.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/TEZ/configuration/tez-site.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HIVE/configuration/hive-env.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HDFS/configuration/hadoop-env.xml * ambari-web/app/data/HDP2.3/site_properties.js * ambari-server/src/main/resources/common-services/HIVE/0.12.0.2.0/configuration/hive-exec-log4j.xml * ambari-server/src/main/resources/stacks/HDP/2.3.GlusterFS/services/OOZIE/configuration/oozie-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/HDFS/configuration/hdfs-site.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/STORM/configuration/ranger-storm-audit.xml * ambari-server/src/main/resources/common-services/KNOX/0.5.0.2.2/configuration/users-ldif.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hadoop-env.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/OOZIE/configuration/oozie-site.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.3/services/STORM/configuration/storm-site.xml * ambari-server/src/main/resources/common-services/OOZIE/4.0.0.2.0/configuration/oozie-log4j.xml * ambari-web/app/data/HDP2/site_properties.js * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration/yarn-log4j.xml * ambari-web/test/data/HDP2.2/site_properties_test.js * ambari-web/app/assets/test/tests.js * ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-admin-site.xml * ambari-server/src/main/resources/stacks/HDP/2.2/services/HBASE/configuration/hbase-env.xml * ambari-server/src/main/resources/common-services/SLIDER/0.60.0.2.2/configuration/slider-log4j.xml * ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/configuration/hdfs-log4j.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/HDFS/configuration/hadoop-env.xml * ambari-server/src/main/resources/common-services/KERBEROS/1.10.3-10/configuration/krb5-conf.xml * ambari-server/src/main/resources/common-services/YARN/2.1.0.2.0/configuration-mapred/mapred-env.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/HBASE/configuration/ranger-hbase-audit.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/KAFKA/configuration/ranger-kafka-plugin-properties.xml * ambari-server/src/main/resources/stacks/HDPWIN/2.1/services/OOZIE/configuration/oozie-env.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/RANGER/configuration/ranger-env.xml * ambari-server/src/main/resources/stacks/HDP/2.3/services/ACCUMULO/configuration/accumulo-log4j.xml * ambari-web/test/data/HDP2.3/site_properties_test.js *
