remove greenplum from source file names

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/3107b669
Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/3107b669
Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/3107b669

Branch: refs/heads/develop
Commit: 3107b6693d54ada8c59f850d54febed682f25a49
Parents: 499d4f0
Author: Lisa Owen <[email protected]>
Authored: Wed Oct 19 11:35:49 2016 -0700
Committer: Lisa Owen <[email protected]>
Committed: Wed Oct 19 11:35:49 2016 -0700

----------------------------------------------------------------------
 ...lum-database-client-applications.html.md.erb | 23 --------------------
 ...awq-database-client-applications.html.md.erb | 23 ++++++++++++++++++++
 ...le-greenplum-file-server-gpfdist.html.md.erb | 13 -----------
 ...example-hawq-file-server-gpfdist.html.md.erb | 13 +++++++++++
 ...ing-data-from-greenplum-database.html.md.erb | 17 ---------------
 ...nloading-data-from-hawq-database.html.md.erb | 17 +++++++++++++++
 ...m-parallel-file-server--gpfdist-.html.md.erb | 19 ----------------
 ...g-the-hawq-file-server--gpfdist-.html.md.erb | 19 ++++++++++++++++
 8 files changed, 72 insertions(+), 72 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/clientaccess/g-greenplum-database-client-applications.html.md.erb
----------------------------------------------------------------------
diff --git a/clientaccess/g-greenplum-database-client-applications.html.md.erb 
b/clientaccess/g-greenplum-database-client-applications.html.md.erb
deleted file mode 100644
index a1e8ff3..0000000
--- a/clientaccess/g-greenplum-database-client-applications.html.md.erb
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: HAWQ Client Applications
----
-
-HAWQ comes installed with a number of client utility applications located in 
the `$GPHOME/bin` directory of your HAWQ master host installation. The 
following are the most commonly used client utility applications:
-
-|Name|Usage|
-|----|-----|
-|`createdb`|create a new database|
-|`createlang`|define a new procedural language|
-|`createuser`|define a new database role|
-|`dropdb`|remove a database|
-|`droplang`|remove a procedural language|
-|`dropuser`|remove a role|
-|`psql`|PostgreSQL interactive terminal|
-|`reindexdb`|reindex a database|
-|`vacuumdb`|garbage-collect and analyze a database|
-
-When using these client applications, you must connect to a database through 
the HAWQ master instance. You will need to know the name of your target 
database, the host name and port number of the master, and what database user 
name to connect as. This information can be provided on the command-line using 
the options `-d`, `-h`, `-p`, and `-U` respectively. If an argument is found 
that does not belong to any option, it will be interpreted as the database name 
first.
-
-All of these options have default values which will be used if the option is 
not specified. The default host is the local host. The default port number is 
5432. The default user name is your OS system user name, as is the default 
database name. Note that OS user names and HAWQ user names are not necessarily 
the same.
-
-If the default values are not correct, you can set the environment variables 
`PGDATABASE`, `PGHOST`, `PGPORT`, and `PGUSER` to the appropriate values, or 
use a `psql``~/.pgpass` file to contain frequently-used passwords.

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/clientaccess/g-hawq-database-client-applications.html.md.erb
----------------------------------------------------------------------
diff --git a/clientaccess/g-hawq-database-client-applications.html.md.erb 
b/clientaccess/g-hawq-database-client-applications.html.md.erb
new file mode 100644
index 0000000..a1e8ff3
--- /dev/null
+++ b/clientaccess/g-hawq-database-client-applications.html.md.erb
@@ -0,0 +1,23 @@
+---
+title: HAWQ Client Applications
+---
+
+HAWQ comes installed with a number of client utility applications located in 
the `$GPHOME/bin` directory of your HAWQ master host installation. The 
following are the most commonly used client utility applications:
+
+|Name|Usage|
+|----|-----|
+|`createdb`|create a new database|
+|`createlang`|define a new procedural language|
+|`createuser`|define a new database role|
+|`dropdb`|remove a database|
+|`droplang`|remove a procedural language|
+|`dropuser`|remove a role|
+|`psql`|PostgreSQL interactive terminal|
+|`reindexdb`|reindex a database|
+|`vacuumdb`|garbage-collect and analyze a database|
+
+When using these client applications, you must connect to a database through 
the HAWQ master instance. You will need to know the name of your target 
database, the host name and port number of the master, and what database user 
name to connect as. This information can be provided on the command-line using 
the options `-d`, `-h`, `-p`, and `-U` respectively. If an argument is found 
that does not belong to any option, it will be interpreted as the database name 
first.
+
+All of these options have default values which will be used if the option is 
not specified. The default host is the local host. The default port number is 
5432. The default user name is your OS system user name, as is the default 
database name. Note that OS user names and HAWQ user names are not necessarily 
the same.
+
+If the default values are not correct, you can set the environment variables 
`PGDATABASE`, `PGHOST`, `PGPORT`, and `PGUSER` to the appropriate values, or 
use a `psql``~/.pgpass` file to contain frequently-used passwords.

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/datamgmt/load/g-example-greenplum-file-server-gpfdist.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/load/g-example-greenplum-file-server-gpfdist.html.md.erb 
b/datamgmt/load/g-example-greenplum-file-server-gpfdist.html.md.erb
deleted file mode 100644
index a0bf669..0000000
--- a/datamgmt/load/g-example-greenplum-file-server-gpfdist.html.md.erb
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Example - HAWQ file server (gpfdist)
----
-
-``` sql
-=# CREATE WRITABLE EXTERNAL TABLE unload_expenses
-( LIKE expenses )
-LOCATION ('gpfdist://etlhost-1:8081/expenses1.out',
-'gpfdist://etlhost-2:8081/expenses2.out')
-FORMAT 'TEXT' (DELIMITER ',');
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/datamgmt/load/g-example-hawq-file-server-gpfdist.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/load/g-example-hawq-file-server-gpfdist.html.md.erb 
b/datamgmt/load/g-example-hawq-file-server-gpfdist.html.md.erb
new file mode 100644
index 0000000..a0bf669
--- /dev/null
+++ b/datamgmt/load/g-example-hawq-file-server-gpfdist.html.md.erb
@@ -0,0 +1,13 @@
+---
+title: Example - HAWQ file server (gpfdist)
+---
+
+``` sql
+=# CREATE WRITABLE EXTERNAL TABLE unload_expenses
+( LIKE expenses )
+LOCATION ('gpfdist://etlhost-1:8081/expenses1.out',
+'gpfdist://etlhost-2:8081/expenses2.out')
+FORMAT 'TEXT' (DELIMITER ',');
+```
+
+

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/datamgmt/load/g-unloading-data-from-greenplum-database.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/load/g-unloading-data-from-greenplum-database.html.md.erb 
b/datamgmt/load/g-unloading-data-from-greenplum-database.html.md.erb
deleted file mode 100644
index e0690ad..0000000
--- a/datamgmt/load/g-unloading-data-from-greenplum-database.html.md.erb
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Unloading Data from HAWQ
----
-
-A writable external table allows you to select rows from other database tables 
and output the rows to files, named pipes, to applications, or as output 
targets for parallel MapReduce calculations. You can define file-based and 
web-based writable external tables.
-
-This topic describes how to unload data from HAWQ using parallel unload 
(writable external tables) and non-parallel unload (`COPY`).
-
--   **[Defining a File-Based Writable External 
Table](../../datamgmt/load/g-defining-a-file-based-writable-external-table.html)**
-
--   **[Defining a Command-Based Writable External Web 
Table](../../datamgmt/load/g-defining-a-command-based-writable-external-web-table.html)**
-
--   **[Unloading Data Using a Writable External 
Table](../../datamgmt/load/g-unloading-data-using-a-writable-external-table.html)**
-
--   **[Unloading Data Using 
COPY](../../datamgmt/load/g-unloading-data-using-copy.html)**
-
-

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/datamgmt/load/g-unloading-data-from-hawq-database.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/load/g-unloading-data-from-hawq-database.html.md.erb 
b/datamgmt/load/g-unloading-data-from-hawq-database.html.md.erb
new file mode 100644
index 0000000..e0690ad
--- /dev/null
+++ b/datamgmt/load/g-unloading-data-from-hawq-database.html.md.erb
@@ -0,0 +1,17 @@
+---
+title: Unloading Data from HAWQ
+---
+
+A writable external table allows you to select rows from other database tables 
and output the rows to files, named pipes, to applications, or as output 
targets for parallel MapReduce calculations. You can define file-based and 
web-based writable external tables.
+
+This topic describes how to unload data from HAWQ using parallel unload 
(writable external tables) and non-parallel unload (`COPY`).
+
+-   **[Defining a File-Based Writable External 
Table](../../datamgmt/load/g-defining-a-file-based-writable-external-table.html)**
+
+-   **[Defining a Command-Based Writable External Web 
Table](../../datamgmt/load/g-defining-a-command-based-writable-external-web-table.html)**
+
+-   **[Unloading Data Using a Writable External 
Table](../../datamgmt/load/g-unloading-data-using-a-writable-external-table.html)**
+
+-   **[Unloading Data Using 
COPY](../../datamgmt/load/g-unloading-data-using-copy.html)**
+
+

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/datamgmt/load/g-using-the-greenplum-parallel-file-server--gpfdist-.html.md.erb
----------------------------------------------------------------------
diff --git 
a/datamgmt/load/g-using-the-greenplum-parallel-file-server--gpfdist-.html.md.erb
 
b/datamgmt/load/g-using-the-greenplum-parallel-file-server--gpfdist-.html.md.erb
deleted file mode 100644
index 0c68b2c..0000000
--- 
a/datamgmt/load/g-using-the-greenplum-parallel-file-server--gpfdist-.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Using the HAWQ File Server (gpfdist)
----
-
-The `gpfdist` protocol provides the best performance and is the easiest to set 
up. `gpfdist` ensures optimum use of all segments in your HAWQ system for 
external table reads.
-
-This topic describes the setup and management tasks for using `gpfdist` with 
external tables.
-
--   **[About gpfdist Setup and 
Performance](../../datamgmt/load/g-about-gpfdist-setup-and-performance.html)**
-
--   **[Controlling Segment 
Parallelism](../../datamgmt/load/g-controlling-segment-parallelism.html)**
-
--   **[Installing gpfdist](../../datamgmt/load/g-installing-gpfdist.html)**
-
--   **[Starting and Stopping 
gpfdist](../../datamgmt/load/g-starting-and-stopping-gpfdist.html)**
-
--   **[Troubleshooting 
gpfdist](../../datamgmt/load/g-troubleshooting-gpfdist.html)**
-
-

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/3107b669/datamgmt/load/g-using-the-hawq-file-server--gpfdist-.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/load/g-using-the-hawq-file-server--gpfdist-.html.md.erb 
b/datamgmt/load/g-using-the-hawq-file-server--gpfdist-.html.md.erb
new file mode 100644
index 0000000..0c68b2c
--- /dev/null
+++ b/datamgmt/load/g-using-the-hawq-file-server--gpfdist-.html.md.erb
@@ -0,0 +1,19 @@
+---
+title: Using the HAWQ File Server (gpfdist)
+---
+
+The `gpfdist` protocol provides the best performance and is the easiest to set 
up. `gpfdist` ensures optimum use of all segments in your HAWQ system for 
external table reads.
+
+This topic describes the setup and management tasks for using `gpfdist` with 
external tables.
+
+-   **[About gpfdist Setup and 
Performance](../../datamgmt/load/g-about-gpfdist-setup-and-performance.html)**
+
+-   **[Controlling Segment 
Parallelism](../../datamgmt/load/g-controlling-segment-parallelism.html)**
+
+-   **[Installing gpfdist](../../datamgmt/load/g-installing-gpfdist.html)**
+
+-   **[Starting and Stopping 
gpfdist](../../datamgmt/load/g-starting-and-stopping-gpfdist.html)**
+
+-   **[Troubleshooting 
gpfdist](../../datamgmt/load/g-troubleshooting-gpfdist.html)**
+
+

Reply via email to