[HDDS-1469] Generate default configuration fragments based on annotations

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: pull-request-available
• Target Version/s: 0.5.0
• Assignee: Marton Elek
• Reporter: Marton Elek
• Created: 25/Apr/19 13:26
• Updated: 02/May/19 12:24
• Resolved: 02/May/19 10:21

Description

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.)

Issue Links

• links to: GitHub Pull Request #773