hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1469) Generate default configuration fragments based on annotations
Date Thu, 02 May 2019 10:34:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831536#comment-16831536
] 

Hudson commented on HDDS-1469:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16490 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/16490/])
HDDS-1469. Generate default configuration fragments based on annotations (elek: rev e2f0f7267791051b561a6e291a22bbc58c34d068)
* (delete) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/conf/ConfigGroup.java
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/ConfigTag.java
* (edit) hadoop-hdds/common/src/test/java/org/apache/hadoop/hdds/conf/SimpleConfiguration.java
* (edit) hadoop-hdds/common/src/test/java/org/apache/hadoop/hdds/conf/TestOzoneConfiguration.java
* (delete) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/conf/ConfigType.java
* (edit) hadoop-hdds/common/src/main/resources/ozone-default.xml
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/Config.java
* (add) hadoop-ozone/integration-test/src/test/resources/hdfs-site.xml
* (delete) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/conf/Config.java
* (add) hadoop-hdds/config/src/test/java/org/apache/hadoop/hdds/conf/TestConfigFileAppender.java
* (add) hadoop-hdds/config/pom.xml
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/ConfigurationException.java
* (edit) hadoop-hdds/pom.xml
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/ConfigFileGenerator.java
* (add) hadoop-ozone/integration-test/src/test/resources/core-site.xml
* (edit) hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/container/ReplicationManager.java
* (delete) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/conf/ConfigurationException.java
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/package-info.java
* (add) hadoop-hdds/config/src/test/java/org/apache/hadoop/hdds/conf/package-info.java
* (edit) hadoop-hdds/common/pom.xml
* (edit) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/conf/OzoneConfiguration.java
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/ConfigFileAppender.java
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/ConfigGroup.java
* (add) hadoop-hdds/config/src/main/java/org/apache/hadoop/hdds/conf/ConfigType.java
* (add) hadoop-hdds/config/src/main/resources/META-INF/services/javax.annotation.processing.Processor
* (add) hadoop-hdds/config/src/test/java/org/apache/hadoop/hdds/conf/ConfigurationExample.java
* (edit) hadoop-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/container/TestReplicationManager.java
* (edit) hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/scm/ScmConfigKeys.java


> Generate default configuration fragments based on annotations
> -------------------------------------------------------------
>
>                 Key: HDDS-1469
>                 URL: https://issues.apache.org/jira/browse/HDDS-1469
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> See the design doc in the parent jira for more details.
> In this jira I introduce a new annotation processor which can generate ozone-default.xml
fragments based on the annotations which are introduced by HDDS-1468.
> The ozone-default-generated.xml fragments can be used directly by the OzoneConfiguration
as I added a small code to the constructor to check ALL the available ozone-default-generated.xml
files and add them to the available resources.
> With this approach we don't need to edit ozone-default.xml as all the configuration can
be defined in java code.
> As a side effect each service will see only the available configuration keys and values
based on the classpath. (If the ozone-default-generated.xml file of OzoneManager is not on
the classpath of the SCM, SCM doesn't see the available configs.) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message