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 #17: Updates for hawq register
Date Fri, 30 Sep 2016 18:56:05 GMT
Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/17#discussion_r81397690
  
    --- Diff: reference/cli/admin_utilities/hawqregister.html.md.erb ---
    @@ -187,5 +168,84 @@ group {
     | varchar  | varchar  |
     
     
    +## <a id="topic1__section5"></a>Options
    +
    +**General Options**
    +
    +<dt>-? (show help) </dt>  
    +<dd>Show help, then exit.
    +
    +<dt>-\\\-version  </dt> 
    +<dd>Show the version of this utility, then exit.</dd>
    +
    +
    +**Connection Options**
    +
    +<dt>-h , -\\\-host \<hostname\> </dt>
    +<dd>Specifies the host name of the machine on which the HAWQ master database server
is running. If not specified, reads from the environment variable `$PGHOST` or defaults to
`localhost`.</dd>
    +
    +<dt> -p , -\\\-port \<port\> </dt> 
    +<dd>Specifies the TCP port on which the HAWQ master database server is listening
for connections. If not specified, reads from the environment variable `$PGPORT` or defaults
to 5432.</dd>
    +
    +<dt>-U , -\\\-user \<username\> </dt> 
    +<dd>The database role name to connect as. If not specified, reads from the environment
variable `$PGUSER` or defaults to the current system user name.</dd>
    +
    +<dt>-d  , -\\\-database \<databasename\>  </dt>
    +<dd>The database to register the Parquet HDFS data into. The default is `postgres`<dd>
    +
    +<dt>-f , -\\\-filepath \<hdfspath\></dt>
    +<dd>The path of the file or directory in HDFS containing the files to be registered.</dd>
    + 
    +<dt>\<tablename\> </dt>
    +<dd>The HAWQ table that will store the data to be registered. If the --config option
is not supplied, the table cannot use hash distribution. Random table distribution is strongly
preferred. If hash distribution must be used, make sure that the distribution policy for the
data files described in the YAML file is consistent with the table being registered into.</dd>
    +
    +####Miscellaneous Options
    +
    +The following options are used with specific use models.
    +
    +<dt>-e , -\\\-eof \<eof\></dt>
    +<dd>Specify the end of the file to be registered. \<eof\> represents the
valid content length of the file, in bytes to be used, a value between 0 the actual size of
the file. If this option is not included, the actual file size, or size of files within a
folder, is used. Used with Use Model 1.</dd>
    +
    +<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 Use Model 2.</dd>
    +
    +<dt>-c , -\\\-config \<yml_config\> </dt> 
    +<dd>Registers files specified by YAML-format configuration files into HAWQ. Used
with Use Model 2.</dd>
    --- End diff --
    
    Change Use -> Usage


---
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.
---

Mime
View raw message