[jira] [Commented] (HAWQ-1376) docs - better describe the pxf host and port settings

2017-03-10 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905614#comment-15905614
 ] 

ASF GitHub Bot commented on HAWQ-1376:
--

Github user lisakowen closed the pull request at:

https://github.com/apache/incubator-hawq-docs/pull/99


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


[jira] [Commented] (HAWQ-1376) docs - better describe the pxf host and port settings

2017-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15904077#comment-15904077
 ] 

ASF GitHub Bot commented on HAWQ-1376:
--

Github user lisakowen commented on a diff in the pull request:

https://github.com/apache/incubator-hawq-docs/pull/99#discussion_r105300059
  
--- Diff: 
markdown/admin/HAWQFilespacesandHighAvailabilityEnabledHDFS.html.md.erb ---
@@ -240,3 +240,7 @@ For command-line administrators:
$ hawq init standby -n -M fast
 
```
+
+## Using PXF with HDFS NameNode HA
+
+When HDFS NameNode High Availability is enabled, identify the HDFS 
Nameservice ID in the `LOCATION` clause \ field when invoking any PXF 
`CREATE EXTERNAL TABLE` command. If the \ 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 --

thanks for reviewing @dyozie.  i've pushed your requested change.


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


[jira] [Commented] (HAWQ-1376) docs - better describe the pxf host and port settings

2017-03-09 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
 
```
+
+## Using PXF with HDFS NameNode HA
+
+When HDFS NameNode High Availability is enabled, identify the HDFS 
Nameservice ID in the `LOCATION` clause \ field when invoking any PXF 
`CREATE EXTERNAL TABLE` command. If the \ 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)


[jira] [Commented] (HAWQ-1376) docs - better describe the pxf host and port settings

2017-03-07 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900437#comment-15900437
 ] 

ASF GitHub Bot commented on HAWQ-1376:
--

GitHub user lisakowen opened a pull request:

https://github.com/apache/incubator-hawq-docs/pull/99

HAWQ-1376 - clarify pxf host and port description

clarify the pxf host and port description (create external table, location 
clause URI) across the docs
- host - any pxf node
- port - the pxf port.  if omitted, HDFS high availability is assumed and 
host is taken to be the HDFS nameservice id, and pxf_service_port value is used 
for the port (default 51200)

also added "using pxf with HA enabled HDFS" section to HA doc, identifying 
HA implications on PXF.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lisakowen/incubator-hawq-docs 
feature/HAWQ-1376-pxfclarify

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq-docs/pull/99.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #99


commit 12d0f4be1b3181c46bf322a7be5c0e9767cdd843
Author: Lisa Owen 
Date:   2017-03-07T01:12:15Z

HAWQ-1376 - clarify pxf host and port description




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