[
https://issues.apache.org/jira/browse/AMBARI-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189731#comment-15189731
]
Jayush Luniya commented on AMBARI-13364:
----------------------------------------
[~jmarron] [~tctruong213] [~afernandez]
Overall, I am in line with the approach to make stack features config driven.
However, instead of having a config property for each feature with
stack_version_<feature>_support, stack_version_<feature>_unsupport, we should
come up with a general solution for stack featurization. Attached is a sample
patch for HDFS + ZOOKEEPER. The code will be a lot cleaner and we dont have to
add a bunch of variables in params.py one for each feature.
As in the patch: HDP-2.1 has stack_features = "snappy", HDP-2.2 has
stack_features = "ru, ranger" and HDP-2.3 has stack_features = "ru,ranger,nfs".
- "snappy" feature support has been removed in HDP-2.2+
- "ru", "ranger" features have been added to HDP-2.2+
- "nfs" feature support has been added to HDP-2.3+
Of course there are more sophisticated scenarios like a feature added from a
specific maintenance release (Example:
https://issues.apache.org/jira/browse/AMBARI-13975)
Thoughts?
> Parameterize stack information used by common services
> -------------------------------------------------------
>
> Key: AMBARI-13364
> URL: https://issues.apache.org/jira/browse/AMBARI-13364
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
> Reporter: Tuong Truong
> Assignee: Juanjo Marron
> Attachments: AMBARI-13364 Parameterize stack information used by
> common services.pdf, AMBARI-13364.patch, stack_featurizer.patch
>
>
> This feature will add a basic framework to remove hardcoded stack information
> out of the common services and use parameter to get access to stack
> information. Currently, common services hardcodes much information specific
> to Hortonworks' HDP stack including name (HDP), specific versions (2.0, 2.1,
> 2.2), and install location. This feature will propose a way of
> configuration these information and parameterize them into the services for
> reference as require.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
