You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lisa Owen (JIRA)" <ji...@apache.org> on 2017/08/01 00:14:00 UTC

[jira] [Commented] (HAWQ-1245) can HAWQ support alternate python module deployment directory?

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

Lisa Owen commented on HAWQ-1245:
---------------------------------

hi [~rlei],

now that HAWQ is using the system python installation, need to have root/sudo access to install any python modules that might be used in pl/pythonu UDFs.  not all HAWQ admins may have such root access.  if it is not possible to create an alternate, gpadmin-owned python module install directory (which would allow gpadmin to install modules there), then i guess there is not much we can do here; feel free to close this issue.

> can HAWQ support alternate python module deployment directory?
> --------------------------------------------------------------
>
>                 Key: HAWQ-1245
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1245
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Command Line Tools
>            Reporter: Lisa Owen
>            Assignee: Radar Lei
>            Priority: Minor
>
> HAWQ no longer embeds python and is now using the system python installation.  with this change, installing a new python module now requires root/sudo access to the system python directories.  is there any reason why HAWQ would not be able to support deploying python modules to an alternate directory that is owned by gpadmin?  or using a python virtual environment?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)