Additional mention of hawq extract
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/73b8d8db Tree: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/tree/73b8d8db Diff: http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/diff/73b8d8db Branch: refs/heads/develop Commit: 73b8d8db0eabb4293efaae92810c912c9f68d6e9 Parents: 285c92b Author: Jane Beckman <[email protected]> Authored: Tue Oct 18 14:13:08 2016 -0700 Committer: Jane Beckman <[email protected]> Committed: Tue Oct 18 14:13:08 2016 -0700 ---------------------------------------------------------------------- datamgmt/load/g-register_files.html.md.erb | 11 +++++++---- reference/cli/admin_utilities/hawqregister.html.md.erb | 2 +- 2 files changed, 8 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/73b8d8db/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 dc2c8e1..79f87ad 100644 --- a/datamgmt/load/g-register_files.html.md.erb +++ b/datamgmt/load/g-register_files.html.md.erb @@ -82,10 +82,9 @@ Data is registered according to the following conditions: - 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. If hash tables are to be registered, the distribution policy in the YAML file must match that of the table being registered into. - -In registering hash tables, the size of the registered file should be identical to or a multiple of the hash table bucket number. When registering hash distributed tables using a YAML file, the order of the files in the YAML file should reflect the hash distribution. +Tables using random distribution are preferred for registering into HAWQ. +There are additional restrictions when registering hash tables. When registering hash-distributed tables using a YAML file, the distribution policy in the YAML file must match that of the table being registered into and the order of the files in the YAML file should reflect the hash distribution. The size of the registered file should be identical to or a multiple of the hash table bucket number. ###Example: Registration using a YAML Configuration File @@ -118,7 +117,7 @@ Select the new table and check to verify that the content has been registered. ## <a id="topic1__section4"></a>Data Type Mapping<a id="topic1__section4"></a> -HIVE and Parquet tables use different data types than HAWQ tables. Mapping must be used for metadata compatibility. You are responsible for making sure your implementation is mapped to the appropriate data type before running `hawq register`. The tables below show equivalent data types, if available. +HIVE and Parquet tables use different data types than HAWQ tables and must be mapped for metadata compatibility. You are responsible for making sure your implementation is mapped to the appropriate data type before running `hawq register`. The tables below show equivalent data types, if available. <span class="tablecap">Table 1. HAWQ to Parquet Mapping</span> @@ -208,5 +207,9 @@ group { | varchar | varchar | +### Extracting Metadata + +For more information on extracting metadata to a YAML file and the output content of the YAML file, refer to the reference page for [hawq extract](hawqextract.html#topic1). + http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/73b8d8db/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 2f1259b..21a8dd8 100644 --- a/reference/cli/admin_utilities/hawqregister.html.md.erb +++ b/reference/cli/admin_utilities/hawqregister.html.md.erb @@ -56,7 +56,7 @@ Two usage models are available. Metadata for the Parquet file(s) and the destination table must be consistent. Different data types are used by HAWQ tables and Parquet files, so the data is mapped. Refer to the section [Data Type Mapping](hawqregister.html#topic1__section7) below. You must verify that the structure of the Parquet files and the HAWQ table are compatible before running `hawq register`. ####Limitations -Only HAWQ or Hive-generated Parquet tables are supported. Partitioned tables are supported, but only single-level partitioned tables can be registered. +Only HAWQ or Hive-generated Parquet tables are supported. Partitioned tables are supported, but only single-level partitioned tables can be registered into HAWQ. Hash tables are not supported in this use model. ###Usage Model 2: Use information from a YAML configuration file to register data
