You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Radar Lei (JIRA)" <ji...@apache.org> on 2017/07/28 09:07: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=16104693#comment-16104693 ] 

Radar Lei commented on HAWQ-1245:
---------------------------------

[~lisakowen] We removed some of the python modules from HAWQ source code due to license/compatible issues. Now user need to manage these modules by themselves.

Base on above, I can't see what we can do since user environment is quite different. Please advice if you have good solution. Thanks.

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