瀏覽代碼

Removes Oozie password override from HDP 2.1 stack

When an Ambari Blueprint is exported from a running cluster
  based on the HDP 2.1 stack, and including Oozie, an Oozie
  password will be included in the exported Blueprint.

This is incorrect behavior, since no password data should
  be available in the exported Blueprint. The Blueprint
  processing code relies on the HDP stack definitions in
  order to determine which fields are passwords.

This patch addresses this problem by removing the Oozie
  password field form the HDP 2.1 stack definition.  The HDP
  2.0.6 stack (which is a parent of the 2.1 stack) already
  includes the correct metadata for this password field, such
  that the Blueprint processor will keep this field out of
  an exported Blueprint as expected.  Since there is no need
  to override this property in the 2.1 stack, the correct
  metadata can be inherited from the 2.0.6 stack.
Bob Nettleton 10 年之前
父節點
當前提交
353daeb940

+ 0 - 11
ambari-server/src/main/resources/stacks/HDP/2.1/services/OOZIE/configuration/oozie-site.xml

@@ -221,17 +221,6 @@
     </description>
     </description>
   </property>
   </property>
 
 
-  <property>
-    <name>oozie.service.JPAService.jdbc.password</name>
-    <value> </value>
-    <description>
-      DB user password.
-
-      IMPORTANT: if password is emtpy leave a 1 space string, the service trims the value,
-      if empty Configuration assumes it is NULL.
-    </description>
-  </property>
-
   <property>
   <property>
     <name>oozie.service.JPAService.pool.max.active.conn</name>
     <name>oozie.service.JPAService.pool.max.active.conn</name>
     <value>10</value>
     <value>10</value>