[ 
https://issues.apache.org/jira/browse/HAWQ-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15802991#comment-15802991
 ] 

ASF GitHub Bot commented on HAWQ-1209:
--------------------------------------

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

    https://github.com/apache/incubator-hawq-docs/pull/80#discussion_r94880323
  
    --- Diff: admin/setuphawqopenv.html.md.erb ---
    @@ -0,0 +1,81 @@
    +---
    +title: Introducing the HAWQ Operating Environment
    +---
    +
    +Before invoking operations on a HAWQ cluster, you must set up your HAWQ 
environment. This set up is required for both administrative and 
non-administrative HAWQ users.
    +
    +## <a id="hawq_setupenv"></a>Procedure: Setting Up Your HAWQ Operating 
Environment
    +
    +HAWQ installs a script that you can use to set up your HAWQ cluster 
environment. The `greenplum_path.sh` script, located in your HAWQ root install 
directory, sets `$PATH` and other environment variables to find HAWQ files.  
Most importantly, `greenplum_path.sh` sets the `$GPHOME` environment variable 
to point to the root directory of the HAWQ installation.  If you installed HAWQ 
from a product distribution, the HAWQ root is typically `/usr/local/hawq`. If 
you built HAWQ from source or downloaded the tarball, you will have selected an 
install root directory on your own.
    +
    +Perform the following steps to set up your HAWQ operating environment:
    +
    +1. Log in to the HAWQ \<node\-type\> system as the desired user.  For 
example:
    +
    +    ``` shell
    +    $ ssh gpadmin@<master>
    +    gpadmin@master$ 
    +    ```
    +
    +    Or, if you are already logged in to \<node\-type\> as a different 
user, switch to the desired user. For example:
    +    
    +    ``` shell
    +    gpadmin@master$ su - <hawq-user>
    +    Password:
    +    hawq-user@master$ 
    +    ```
    +
    +2. Set up your HAWQ operating environment by sourcing the 
`greenplum_path.sh` file. For HAWQ deployments installed from a product 
distribution:
    +
    +    ``` shell
    +    hawq-node$ source /usr/local/hawq/greenplum_path.sh
    +    ```
    +
    +    If you built HAWQ from source or downloaded the tarball, substitute 
the path to the installed or extracted `greenplum_path.sh` file \(for example 
`/opt/hawq-2.1.0.0/greenplum_path.sh`\).
    +
    +
    +3. Edit your `.bash_profile` or other shell initialization file to source 
`greenplum_path.sh` on login.  For example, add:
    +
    +    ``` shell
    +    source /usr/local/hawq/greenplum_path.sh
    --- End diff --
    
    This and a few of the following command blocks are omitting the shell 
prompt.


> docs - create an overview page for HAWQ
> ---------------------------------------
>
>                 Key: HAWQ-1209
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1209
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Lisa Owen
>            Assignee: David Yozie
>            Priority: Minor
>
> create a "landing" topic that ties together the components in the HAWQ 
> operating environment and the relevant documentation contents/sections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to