hawq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yo...@apache.org
Subject [1/3] incubator-hawq-docs git commit: misc doc clarifications
Date Tue, 20 Sep 2016 16:08:16 GMT
Repository: incubator-hawq-docs
Updated Branches:
  refs/heads/develop 1661c625d -> c617b1c10

misc doc clarifications

Project: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/commit/cd4a3db2
Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/cd4a3db2
Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/cd4a3db2

Branch: refs/heads/develop
Commit: cd4a3db248a2b882683dc496c9f07872b0cb2783
Parents: 1661c62
Author: Lisa Owen <lowen@pivotal.io>
Authored: Mon Sep 19 10:44:24 2016 -0700
Committer: Lisa Owen <lowen@pivotal.io>
Committed: Mon Sep 19 10:44:24 2016 -0700

 install/aws-config.html.md.erb               | 18 ++----------------
 pxf/HawqExtensionFrameworkPXF.html.md.erb    |  4 ++++
 reference/HAWQDataTypes.html.md.erb          |  4 +++-
 requirements/system-requirements.html.md.erb |  3 +++
 4 files changed, 12 insertions(+), 17 deletions(-)

diff --git a/install/aws-config.html.md.erb b/install/aws-config.html.md.erb
index 395970b..fb2a623 100644
--- a/install/aws-config.html.md.erb
+++ b/install/aws-config.html.md.erb
@@ -29,9 +29,7 @@ Instance store-backed storage is generally better performing than EBS and
 **Note** EC2 *instance store* provides temporary block-level storage. This storage is located
on disks that are physically attached to the host computer. While instance store provides
high performance, powering off the instance causes data loss. Soft reboots preserve instance
store data. 
 Virtual devices for instance store volumes for HAWQ EC2 instance store instances are named
`ephemeralN` (where *N* varies based on instance type). CentOS instance store block device
are named `/dev/xvdletter` (where *letter* is a lower case letter of the alphabet).
 ### <a id="topic_cfgplacegrp"></a>Configure Placement Group 
@@ -75,24 +73,14 @@ Ensure your Ambari and HAWQ master instances are each assigned a public
IP addre
 A security group is a set of rules that control network traffic to and from your HAWQ instance.
 One or more rules may be associated with a security group, and one or more security groups
may be associated with an instance.
-To configure HAWQ communication between nodes in the HAWQ cluster, include and open the following
ports in the appropriate security group for the HAWQ master and segment nodes:
-?? PROVIDE SPECIFIC type/protocol/portrange/source settings from EC2 console ??
+To configure HAWQ communication between nodes in the HAWQ cluster, include and open the following
ports in the appropriate security group for the HAWQ master and segment nodes.
 | Port  | Application |
 | 22    | ssh - secure connect to other hosts |
-| XX  | XX |  
-UDP access within the VPC should be enabled by default.
 To allow access to/from a source external to the Ambari management node, include and open
the following ports in an appropriate security group for your Ambari node:
-?? PROVIDE SPECIFIC type/protocol/portrange/source settings from EC2 console ??
 | Port  | Application |
 | 22    | ssh - secure connect to other hosts |
@@ -116,8 +104,6 @@ After launching your HAWQ instance, you will connect to and configure
the instan
 Before installing HAWQ, set up the EC2 instances as you would local host server machines.
Configure the host operating system, configure host network information (for example, update
the `/etc/hosts` file), set operating system parameters, and install operating system packages.
For information about how to prepare your operating system environment for HAWQ, see [Select
HAWQ Host Machines](../install/select-hosts.html).
 ##References<a id="topic_hgz_zwy_bv"></a>

diff --git a/pxf/HawqExtensionFrameworkPXF.html.md.erb b/pxf/HawqExtensionFrameworkPXF.html.md.erb
index b705984..c0d7c0f 100644
--- a/pxf/HawqExtensionFrameworkPXF.html.md.erb
+++ b/pxf/HawqExtensionFrameworkPXF.html.md.erb
@@ -28,6 +28,10 @@ PXF allows users to create custom connectors to access other parallel data
     This topic describes how to access HBase data using PXF.
+-   **[Accessing JSON Data](../pxf/JsonPXF.html)**
+    This topic describes how to access JSON data using PXF.
 -   **[Using Profiles to Read and Write Data](../pxf/ReadWritePXF.html)**
     PXF profiles are collections of common metadata attributes that can be used to simplify
the reading and writing of data. You can use any of the built-in profiles that come with PXF
or you can create your own.

diff --git a/reference/HAWQDataTypes.html.md.erb b/reference/HAWQDataTypes.html.md.erb
index d894b38..fe5cff7 100644
--- a/reference/HAWQDataTypes.html.md.erb
+++ b/reference/HAWQDataTypes.html.md.erb
@@ -27,7 +27,7 @@ The following data types are specified by SQL:
 -   timestamp (with or without time zone)
 -   varchar
-**Note**: HAWQ supports the array data type for append-only tables; parquet table storage
does *not* support the array type. 
+**Note**(\*): HAWQ supports the array data type for append-only tables; parquet table storage
does *not* support the array type. 
 Each data type has an external representation determined by its input and output functions.
Many of the built-in types have obvious external formats. However, several types are unique
to HAWQ, such as geometric paths, or have several possibilities for formats, such as the date
and time types. Some of the input and output functions are not invertible. That is, the result
of an output function may lose accuracy when compared to the original input.
@@ -75,6 +75,8 @@ Each data type has an external representation determined by its input and
 For variable length data types (such as char, varchar, text, xml, etc.) if the data is greater
than or equal to 127 bytes, the storage overhead is 4 bytes instead of 1.
+**Note**: Use these documented built-in types when creating user tables.  Any other data
types that might be visible in the source code are for internal use only.
 ## <a id="timezones"></a>Time Zones
 Time zones, and time-zone conventions, are influenced by political decisions, not just earth
geometry. Time zones around the world became somewhat standardized during the 1900's, but
continue to be prone to arbitrary changes, particularly with respect to daylight-savings rules. HAWQ uses
the widely-used zoneinfo time zone database for information about historical time zone rules.
For times in the future, the assumption is that the latest known rules for a given time zone
will continue to be observed indefinitely far into the future.

diff --git a/requirements/system-requirements.html.md.erb b/requirements/system-requirements.html.md.erb
index bc08ef0..35a2ed9 100644
--- a/requirements/system-requirements.html.md.erb
+++ b/requirements/system-requirements.html.md.erb
@@ -187,6 +187,9 @@ If this system uses the default HAWQ resource manager, you would set `hawq_rm_me
 -   Dedicated, non-blocking switch.
 -   Systems with multiple NICs require NIC bonding to utilize all available network bandwidth.
+## <a id="topic_rdb_jhv_2v"></a>Networking Requirements
+Communications between the HAWQ master and segments require reverse DNS lookup be configured
in your cluster network.
 ## <a id="port-req"></a>Port Requirements
 Individual PXF plug-ins, which you install after adding the HAWQ and PXF services, require
that you Tomcat on the host machine. Tomcat reserves ports 8005, 8080, and 8009.

View raw message