[ 
https://issues.apache.org/jira/browse/IMPALA-6808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Armstrong updated IMPALA-6808:
----------------------------------
    Target Version: Product Backlog
          Priority: Major  (was: Critical)

I'm just going to change the status and target since the number of critical 
JIRAs is a bit overwhelming and a lot of them are arguably not critical - this 
seems like it would be a great improvement regardless
.

> Impala python code should be installed into infra/python/env like other 
> packages
> --------------------------------------------------------------------------------
>
>                 Key: IMPALA-6808
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6808
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Clients, Infrastructure
>    Affects Versions: Impala 3.0, Impala 2.12.0
>            Reporter: David Knupp
>            Assignee: David Knupp
>            Priority: Major
>
> Impala/infra/python/env is the environment where necessary upstream python 
> libraries and packages get installed -- e.g., the packages listed in 
> https://github.com/apache/impala/blob/master/infra/python/deps/requirements.txt
>  and other similar files.
> Impala's own internal python code (like the impala-shell, or the common test 
> libraries that we rely upon) should be made available the same way -- as 
> actual packages installed into the environment -- rather than by resorting to 
> PYTHONPATH/sys.path sleight-of-hand, performed by such as 
> bin/set-pythonpath.sh and bin/impala-python-common.sh.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to