hawq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From li...@apache.org
Subject incubator-hawq-docs git commit: create external table - correct formatting error
Date Fri, 21 Jul 2017 19:20:50 GMT
Repository: incubator-hawq-docs
Updated Branches:
  refs/heads/master 776ede0e5 -> 39cd81475


create external table - correct formatting error


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

Branch: refs/heads/master
Commit: 39cd814753136cb8b925aec68dca0907ac20b276
Parents: 776ede0
Author: Lisa Owen <lowen@pivotal.io>
Authored: Fri Jul 21 12:19:59 2017 -0700
Committer: Lisa Owen <lowen@pivotal.io>
Committed: Fri Jul 21 12:19:59 2017 -0700

----------------------------------------------------------------------
 markdown/reference/sql/CREATE-EXTERNAL-TABLE.html.md.erb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-hawq-docs/blob/39cd8147/markdown/reference/sql/CREATE-EXTERNAL-TABLE.html.md.erb
----------------------------------------------------------------------
diff --git a/markdown/reference/sql/CREATE-EXTERNAL-TABLE.html.md.erb b/markdown/reference/sql/CREATE-EXTERNAL-TABLE.html.md.erb
index c458cae..8cb661b 100644
--- a/markdown/reference/sql/CREATE-EXTERNAL-TABLE.html.md.erb
+++ b/markdown/reference/sql/CREATE-EXTERNAL-TABLE.html.md.erb
@@ -183,7 +183,7 @@ For writable external tables, specifies the URI location of the `gpfdist`
proces
 
 With two `gpfdist` locations listed as in the above example, half of the segments would send
their output data to the `data1.out` file and the other half to the `data2.out` file.
 
-For the `pxf` protocol, the `LOCATION` string specifies the HDFS NameNode \<host\>
and the \<port\> of the PXF service, the location of the data, and the PXF profile or
Java classes used to convert the data between storage format and HAWQ format. If the \<port\>
is omitted, the \<host\> is taken to be the logical name for the high availability Nameservice,
and the \<port\> is the value of the `pxf_service_port` configuration parameter, 51200
by default. The URL parameters `FRAGMENTER`, `ACCESSOR`, and `RESOLVER` are the names of PXF
plug-ins (Java classes) that convert between the external data format and HAWQ data format.
The `FRAGMENTER` parameter is only used with readable external tables. PXF allows combinations
of these parameters to be configured as profiles so that a single `PROFILE` parameter can
be specified to access external data, for example `?PROFILE=Hive`. Additional \<custom-options\>`
can be added to the LOCATION URI to further describe the external data format or st
 orage options. For details about the plug-ins and profiles provided with PXF and information
about creating custom plug-ins for other data sources see [Using PXF with Unmanaged Data](../../pxf/HawqExtensionFrameworkPXF.html).</dd>
+For the `pxf` protocol, the `LOCATION` string specifies the HDFS NameNode \<host\>
and the \<port\> of the PXF service, the location of the data, and the PXF profile or
Java classes used to convert the data between storage format and HAWQ format. If the \<port\>
is omitted, the \<host\> is taken to be the logical name for the high availability Nameservice,
and the \<port\> is the value of the `pxf_service_port` configuration parameter, 51200
by default. The URL parameters `FRAGMENTER`, `ACCESSOR`, and `RESOLVER` are the names of PXF
plug-ins (Java classes) that convert between the external data format and HAWQ data format.
The `FRAGMENTER` parameter is only used with readable external tables. PXF allows combinations
of these parameters to be configured as profiles so that a single `PROFILE` parameter can
be specified to access external data, for example `?PROFILE=Hive`. Additional \<custom-option\>s
can be added to the LOCATION URI to further describe the external data format or sto
 rage options. For details about the plug-ins and profiles provided with PXF and information
about creating custom plug-ins for other data sources see [Using PXF with Unmanaged Data](../../pxf/HawqExtensionFrameworkPXF.html).</dd>
 
 <dt>EXECUTE '\<command\>' ON ...  </dt>
 <dd>Allowed for readable web external tables or writable external tables only. For
readable web external tables, specifies the OS command to be executed by the segment instances.
The \<command\> can be a single OS command or a script. If \<command\> executes
a script, that script must reside in the same location on all of the segment hosts and be
executable by the HAWQ superuser (`gpadmin`).


Mime
View raw message