[jira] [Commented] (HAWQ-317) PXF supports Secure Isilon Cluster

["Shivram Mani (JIRA)" <ji...@apache.org>]

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

Shivram Mani commented on HAWQ-317:
-----------------------------------

Pull request https://github.com/apache/incubator-hawq/pull/279

Pending certification by [~jpatel3] on secure Isilon cluster.

> PXF supports Secure Isilon Cluster
> ----------------------------------
>
>                 Key: HAWQ-317
>                 URL: https://issues.apache.org/jira/browse/HAWQ-317
>             Project: Apache HAWQ
>          Issue Type: New Feature
>          Components: PXF
>            Reporter: Goden Yao
>            Assignee: Noa Horn
>             Fix For: 2.0.0
>
>
> HAWQ users who use Isilon (EMC storage solution), they expect PXF to work fine with Secure Cluster settings.
> **Background**
> PXF has a separate code path to handle secure cluster scenario: 
> [hd_work_mgr.c | https://github.com/apache/incubator-hawq/blob/81385f09fbbc59b2912b2f8ff9a3edbee6427e9b/src/backend/access/external/hd_work_mgr.c]  generate_delegation_token()
> 8020 is hardcoded for pxf to get security token at the moment. 
> Suppose you defined the table as "....location("pxf://uri:port/...."
> From the code, you can see that , if it's nonHA but secure cluster, pxf will try to get the token from "uri:8020" where "uri" is from user input data.
> For Isilon, as there's no specific name node per say - data nodes are for storage and cannot be installed with PXF, work nodes installed with pxf but don't handle security token request.
> So if user puts a work node uri , it would work with non-secure cluster. When it's secure cluster, it fails. If user puts a Isilon uri there, they can get the security token, but will fail later on when querying as Isilon data nodes don't have pxf installed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)