[
https://issues.apache.org/jira/browse/HAWQ-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15903991#comment-15903991
]
ASF GitHub Bot commented on HAWQ-1376:
--------------------------------------
Github user dyozie commented on a diff in the pull request:
https://github.com/apache/incubator-hawq-docs/pull/99#discussion_r105257794
--- Diff:
markdown/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb ---
@@ -240,3 +240,7 @@ For command-line administrators:
$ hawq init standby -n -M fast
```
+
+## <a id="pxfnhdfsnamenode"></a>Using PXF with HDFS NameNode HA
+
+When HDFS NameNode High Availability is enabled, identify the HDFS
Nameservice ID in the `LOCATION` clause \<host\> field when invoking any PXF
`CREATE EXTERNAL TABLE` command. If the \<port\> is omitted from the `LOCATION`
URI, PXF connects to the port number designated by the `pxf_service_port`
server configuration parameter value (default is 51200).
--- End diff --
Small suggest edit:
**If** HDFS NameNode High Availability is enabled, **use** the HDFS
Nameservice ...
> docs - better describe the pxf host and port settings
> -----------------------------------------------------
>
> Key: HAWQ-1376
> URL: https://issues.apache.org/jira/browse/HAWQ-1376
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Documentation
> Reporter: Lisa Owen
> Assignee: David Yozie
>
> the pxf host and port settings as described some places in the docs as hdfs
> namenode and port. this is confusing - the host does not have to be the
> namenode and the port should be the pxf port.
> clarify the docs in this area.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
