hawq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yo...@apache.org
Subject [7/9] incubator-hawq-docs git commit: Remove --repair option
Date Thu, 27 Oct 2016 19:56:42 GMT
Remove --repair option


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

Branch: refs/heads/develop
Commit: 08951440ec17ad5c82a908e7679da6d2ea8cf648
Parents: 73b8d8d
Author: Jane Beckman <jbeckman@pivotal.io>
Authored: Wed Oct 19 14:05:20 2016 -0700
Committer: Jane Beckman <jbeckman@pivotal.io>
Committed: Wed Oct 19 14:05:20 2016 -0700

----------------------------------------------------------------------
 datamgmt/load/g-register_files.html.md.erb             | 1 -
 reference/cli/admin_utilities/hawqregister.html.md.erb | 6 +-----
 2 files changed, 1 insertion(+), 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/08951440/datamgmt/load/g-register_files.html.md.erb
----------------------------------------------------------------------
diff --git a/datamgmt/load/g-register_files.html.md.erb b/datamgmt/load/g-register_files.html.md.erb
index 79f87ad..97cd637 100644
--- a/datamgmt/load/g-register_files.html.md.erb
+++ b/datamgmt/load/g-register_files.html.md.erb
@@ -80,7 +80,6 @@ Data is registered according to the following conditions:
 -  Existing tables have files appended to the existing HAWQ table.
 -  If a table does not exist, it is created and registered into HAWQ. The catalog table will
be updated with the file size specified by the YAML file.
 -  If the -\\\-force option is used, the data in existing catalog tables is erased and re-registered.
All HDFS-related catalog contents in `pg_aoseg.pg_paqseg_$relid ` are cleared. The original
files on HDFS are retained.
--  If the -\\\-repair option is used, data is rolled back to a specified checkpoint. If the
table already exists, both the file folder and `pg_aoseg.pg_paqseg_$relid` catalog entry are
rolled back to the checkpoint configuration in the YAML file. Files generated after the timestamp
of the checkpoint will be deleted. you cannot redistribute, truncate, or drop hash tables.
Using the -\\\- repair option with redistributed table data will result in an error.
 
 Tables using random distribution are preferred for registering into HAWQ.
 

http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/08951440/reference/cli/admin_utilities/hawqregister.html.md.erb
----------------------------------------------------------------------
diff --git a/reference/cli/admin_utilities/hawqregister.html.md.erb b/reference/cli/admin_utilities/hawqregister.html.md.erb
index 21a8dd8..1bca10e 100644
--- a/reference/cli/admin_utilities/hawqregister.html.md.erb
+++ b/reference/cli/admin_utilities/hawqregister.html.md.erb
@@ -23,7 +23,6 @@ Misc. Options:
      [-f <filepath>] 
 	 [-e <eof>]
  	 [--force]
- 	 [--repair] 
      [-c <yml_config>]  
 hawq register help | -? 
 hawq register --version
@@ -70,7 +69,7 @@ The register process behaves differently, according to different conditions.
 -  Existing tables have files appended to the existing HAWQ table.
 -  If a table does not exist, it is created and registered into HAWQ. 
 -  If the -\\\-force option is used, the data in existing catalog tables is erased and re-registered.
--  If the -\\\-repair option is used, data is rolled back to  the checkpoint configuration
in the YAML file. Files generated after the timestamp of the checkpoint will be deleted. Hash
table redistribution, table truncate, and table drop are not supported.
+
 
 ###Limitations for Registering Hive Tables to HAWQ
 The currently-supported data types for generating Hive tables into HAWQ tables are: boolean,
int, smallint, tinyint, bigint, float, double, string, binary, char, and varchar.  
@@ -210,9 +209,6 @@ The following options are used with specific use models.
 <dt>-F , -\\\-force</dt>
 <dd>Used for disaster recovery of a cluster. Clears all HDFS-related catalog contents
in `pg_aoseg.pg_paqseg_$relid `and re-registers files to a specified table. The HDFS files
are not removed or modified. To use this option for recovery, data is assumed to be periodically
imported to the cluster to be recovered. Used with Usage Model 2.</dd>
 
-<dt>-R , -\\\-repair \<yml_config\> </dt>
-<dd>Rolls data back to a specified checkpoint. If the table already exists, both the
file folder and `pg_aoseg.pg_paqseg_$relid` catalog entry are rolled back to the checkpoint
configuration in the YAML file. Deletes any files generated after the timestamp of the checkpoint.
Used with Usage Model 2.</dd>
-
 <dt>-c , -\\\-config \<yml_config\> </dt> 
 <dd>Registers files specified by YAML-format configuration files into HAWQ. Used with
Usage Model 2.</dd>
 


Mime
View raw message