THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Stack featurization was added as part of the HDP stack configurations on HDP/2.0.6/configuration/cluster-env.xml, introducing a new stack_features property which value is processed in the stack engine from an external property file.
| Code Block | ||||
|---|---|---|---|---|
| ||||
<!-- Define stack_features property in the base stack. DO NOT override this property for each stack version -->
<property>
<name>stack_features</name>
<value/>
<description>List of features supported by the stack</description>
<property-type>VALUE_FROM_PROPERTY_FILE</property-type>
<value-attributes>
<property-file-name>stack_features.json</property-file-name>
<property-file-type>json</property-file-type>
<read-only>true</read-only>
<overridable>false</overridable>
<visible>false</visible>
</value-attributes>
<on-ambari-upgrade add="true"/>
</property> |
Stack Features properties are defined in stack_features.json file under /HDP/2.0.6/properties. These features support is now available for access at service-level code to change certain service behaviors or configurations. This is an example of features described in stack_features.jon file:
| Code Block | ||||
|---|---|---|---|---|
| ||||
"stack_features": [
{
"name": "snappy",
"description": "Snappy compressor/decompressor support",
"min_version": "2.0.0.0",
"max_version": "2.2.0.0"
},
{
"name": "lzo",
"description": "LZO libraries support",
"min_version": "2.2.1.0"
},
{
"name": "express_upgrade",
"description": "Express upgrade support",
"min_version": "2.1.0.0"
},
{
"name": "rolling_upgrade",
"description": "Rolling upgrade support",
"min_version": "2.2.0.0"
}
]
} |