Return-Path: <dev-return-5606-archive-asf-public=cust-asf.ponee.io@hawq.incubator.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 3D895200BE7
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 15 Nov 2016 01:18:55 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 3C3AF160B0D; Tue, 15 Nov 2016 00:18:55 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 8DA9B160B0F
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 15 Nov 2016 01:18:54 +0100 (CET)
Received: (qmail 41236 invoked by uid 500); 15 Nov 2016 00:18:53 -0000
Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@hawq.incubator.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@hawq.incubator.apache.org>
List-Post: <mailto:dev@hawq.incubator.apache.org>
List-Id: <dev.hawq.incubator.apache.org>
Reply-To: dev@hawq.incubator.apache.org
Delivered-To: mailing list dev@hawq.incubator.apache.org
Received: (qmail 41129 invoked by uid 99); 15 Nov 2016 00:18:53 -0000
Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2016 00:18:53 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id EA95D1A05E6
	for <dev@hawq.apache.org>; Tue, 15 Nov 2016 00:18:52 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -7.019
X-Spam-Level: 
X-Spam-Status: No, score=-7.019 tagged_above=-999 required=6.31
	tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01,
	RP_MATCHES_RCVD=-2.999] autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])
	by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024)
	with ESMTP id 3hXvhh48WBMV for <dev@hawq.apache.org>;
	Tue, 15 Nov 2016 00:18:51 +0000 (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 5A96C5FAF3
	for <dev@hawq.incubator.apache.org>; Tue, 15 Nov 2016 00:18:50 +0000 (UTC)
Received: (qmail 32730 invoked by uid 99); 15 Nov 2016 00:17:35 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Nov 2016 00:17:35 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33)
	id 1BBB7E09B6; Tue, 15 Nov 2016 00:17:35 +0000 (UTC)
From: dyozie <git@git.apache.org>
To: dev@hawq.incubator.apache.org
Reply-To: dev@hawq.incubator.apache.org
References: <git-pr-60-incubator-hawq-docs@git.apache.org>
In-Reply-To: <git-pr-60-incubator-hawq-docs@git.apache.org>
Subject: [GitHub] incubator-hawq-docs pull request #60: HAWQ-1151 - add ambari procedures
Content-Type: text/plain
Message-Id: <20161115001735.1BBB7E09B6@git1-us-west.apache.org>
Date: Tue, 15 Nov 2016 00:17:35 +0000 (UTC)
archived-at: Tue, 15 Nov 2016 00:18:55 -0000

Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/60#discussion_r87921176
  
    --- Diff: clientaccess/roles_privs.html.md.erb ---
    @@ -159,47 +159,44 @@ You can set your chosen encryption method system-wide or on a per-session basis.
     
     #### <a id="topic11"></a>System-wide 
     
    -To set the `password_hash_algorithm` server parameter on a complete HAWQ system \(master and its segments\):
    +You will perform different procedures to set the encryption method system-wide depending upon whether you manage your cluster from the command line or use Ambari. If you use Ambari to manage your HAWQ cluster, you must ensure that you update encryption method configuration parameters via the Ambari Web UI only. If you manage your HAWQ cluster from the command line, you will use the `hawq config` command line utility to set encryption method configuration parameters.
     
    -1.  Log into your HAWQ instance as a superuser.
    -2.  Execute `hawq config` with the `password_hash_algorithm` set to `SHA-256` \(or `SHA-256-FIPS` to use the FIPS-compliant libraries for SHA-256\)
    +To set the `password_hash_algorithm` server parameter on all nodes in your HAWQ cluster \(master and its segments\):
    --- End diff --
    
    Remove this line.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---