ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Maron" <>
Subject Re: Review Request 38065: leverage stack advisor to manifest config changes in hive due to atlas availability
Date Thu, 10 Sep 2015 21:59:19 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated Sept. 10, 2015, 9:59 p.m.)

Review request for Ambari, John Speidel, Sumit Mohanty, and Srimanth Gunturi.

Bugs: AMBARI-12978

Repository: ambari


Rather than make modifications that are not visible to the user via the service scripts, the
config changes that are required for hive when atlas is available in the cluster have been
moved to the stack advisor.  Some important points:

1) and are now configuration properties that are defined
in the service's hive-site.xml.  They therefore appear as advanced hive-site properties in
the UI.
2)  When atlas is not installed, these two properties are set to a space so that hopefully
no values are seen in the UI and the 'require-input' attribute of does
not trigger a requirement to specify a value.
3)  When atlas is installed, the is set to a null string and the 'require-input'
property appears to trigger the expected "value required" logic in the UI.  This is important
since the cluster name property defines the namespace for the atlas queries associated with
the given cluster (atlas supports multiple hive instances).

Diffs (updated)

  ambari-server/src/main/resources/stacks/HDP/2.3/services/ c65e110 
  ambari-server/src/test/python/stacks/2.3/common/ bea7d60 



- python unit tests
- installation of clusters:
1)  Hive only followed by addition of atlas
2)  hive and atlas together

(NOTE:  still working thru some of the functional cluster test scenarios but wanted to proceed
with a review process in parallel)


Jonathan Maron

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message