hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dyozie <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #80: HAWQ-1209 - hawq overview page
Date Fri, 06 Jan 2017 00:11:40 GMT
Github user dyozie commented on a diff in the pull request:

    --- Diff: admin/RunningHAWQ.html.md.erb ---
    @@ -2,21 +2,36 @@
     title: Running a HAWQ Cluster
    -This section provides information for system administrators and database superusers responsible
for administering a HAWQ system.
    -This guide provides information and instructions for configuring, maintaining and using
a HAWQ system. This guide is intended for system and database administrators responsible for
managing a HAWQ system.
    -This guide assumes knowledge of Linux/UNIX system administration, database management
systems, database administration, and structured query language \(SQL\). Because HAWQ is based
on PostgreSQL 8.2.15, this guide assumes some familiarity with PostgreSQL. This guide calls
out similarities between HAWQ and PostgreSQL features throughout. It contains the topics:
    -*  <a class="subnav" href="./ambari-admin.html">Managing HAWQ Using Ambari</a>
    -*  <a class="subnav" href="./startstop.html">Starting and Stopping HAWQ</a>
    -*  <a class="subnav" href="./ClusterExpansion.html">Expanding a Cluster</a>
    -*  <a class="subnav" href="./ClusterShrink.html">Removing a Node</a>
    -*  <a class="subnav" href="./BackingUpandRestoringHAWQDatabases.html">Backing Up
and Restoring HAWQ</a>
    -*  <a class="subnav" href="./HighAvailability.html">High Availability in HAWQ</a>
    -*  <a class="subnav" href="./MasterMirroring.html">Master Mirroring</a>
    -*  <a class="subnav" href="./HAWQFilespacesandHighAvailabilityEnabledHDFS.html">HAWQ
Filespaces and High Availability Enabled HDFS</a>
    -*  <a class="subnav" href="./FaultTolerance.html">Understanding the Fault Tolerance
    -*  <a class="subnav" href="./RecommendedMonitoringTasks.html">Recommended Monitoring
and Maintenance Tasks</a>
    -*  <a class="subnav" href="./maintain.html">Routine System Maintenance Tasks</a>
    -*  <a class="subnav" href="./monitor.html">Monitoring a HAWQ System</a>
    +Your HAWQ deployment environment is a collection of systems, processes, and data, and
the users that operate on these systems, processes, and data. This section provides information
for system administrators and database superusers responsible for administering a HAWQ deployment.
    +You should have some knowledge of Linux/UNIX system administration, database management
systems, database administration, and structured query language \(SQL\) to administer a HAWQ
cluster. Because HAWQ is based on PostgreSQL 8.2.15, you should also have some familiarity
with PostgreSQL. The HAWQ documentation calls out similarities between HAWQ and PostgreSQL
features throughout.
    +## <a id="hawq_users"></a>HAWQ Users
    +HAWQ supports users with both administrative and operating privileges. The HAWQ administrator
may choose to manage the HAWQ cluster using either Ambari or the command line. [Managing HAWQ
Using Ambari](../admin/ambari-admin.html) provides Ambari-specific HAWQ cluster administration
procedures. [Starting and Stopping HAWQ](startstop.html), [Expanding a Cluster](ClusterExpansion.html),
and [Removing a Node](ClusterShrink.html) describe specific command-line-managed HAWQ cluster
administration procedures. Other topics in this guide are applicable to both Ambari- and command-line-managed
HAWQ clusters.
    +The default HAWQ admininstrator user is named `gpadmin`. The HAWQ admin may choose to
assign administrative and/or operating HAWQ privileges to additional users.  Refer to [Configuring
Client Authentication](../clientaccess/client_auth.html) and [Managing Roles and Privileges](../clientaccess/roles_privs.html)
for additional information on HAWQ user configuration.
    +## <a id="hawq_systems"></a>HAWQ Deployment Systems
    +A typical HAWQ deployment will include single HDFS and HAWQ master and standby nodes
and multiple HAWQ segment and HDFS data nodes. The HAWQ cluster may also include systems running
PXF and other Hadoop services. Refer to [HAWQ Architecture](../overview/HAWQArchitecture.html)
and [Select HAWQ Host Machines](../install/select-hosts.html) for information about the different
systems in a HAWQ deployment and how they are configured.
    +## <a id="hawq_env_databases"></a>HAWQ Databases
    +[Creating and Managing Databases](../ddl/ddl-database.html) and [Creating and Managing
Tables](../ddl/ddl-table.html) identify specific HAWQ database and table creation and access
    +You manage HAWQ databases at the command line using the [psql](../reference/cli/client_utilities/psql.html)
utility, an interactive front-end to the HAWQ PostgreSQL database. Configuring client access
to HAWQ databases and tables may require information related to [Establishing a Database Session](../clientaccess/g-establishing-a-database-session.html).
    +[HAWQ Database Drivers and APIs](../clientaccess/g-database-application-interfaces.html)
identifies supported HAWQ database drivers and APIs for additional client access methods.
    +## <a id="hawq_env_data"></a>HAWQ Data
    +HAWQ internal data resides in HDFS. You may require access to data in different formats
and locations in your data lake. You can use HAWQ to query both internal and this external
    +- [Managing Data with HAWQ](../datamgmt/dml.html) discusses the basic data operations
and details regarding the loading and unloading semantics for HAWQ internal tables.
    +- [Using PXF with Unmanaged Data](../pxf/HawqExtensionFrameworkPXF.html) describes PXF,
an extensible framework you may use to query data external to HAWQ.
    +## <a id="hawq_env_setup"></a>HAWQ Operating Environment
    +Refer to [Introducing the HAWQ Operating Environment](setuphawqopenv.html) for a discussion
of the HAWQ operating environment, including a procedure to set up the HAWQ environment. This
section also provides and introduction to the important files and directories in a HAWQ installation.
    --- End diff --
    and -> an

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.

View raw message