hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hornn <...@git.apache.org>
Subject [GitHub] incubator-hawq pull request: Writable security fix
Date Thu, 24 Mar 2016 02:33:47 GMT
Github user hornn commented on the pull request:

    https://github.com/apache/incubator-hawq/pull/497#issuecomment-200624680
  
    Not sure I understood everything, so correct me if I am wrong. 
    So right now we have two flows
    1. For readable tables we append dfs_address in hd_work_mgr and parse it in pxfuriparser.
    2. For writable tables we append dfs_address as part of the URI that is part of the external
table context. Then we parse it in gpbridgeapi, but only in the export case (writable).
    My question is - shouldn't we consolidate the two solutions and adopt the 2nd flow for
both readable and writable? 



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