You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2020/10/21 23:27:00 UTC

[jira] [Assigned] (IMPALA-10274) Move impala-python initialization into the CMake build

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

Joe McDonnell reassigned IMPALA-10274:
--------------------------------------

    Assignee: Joe McDonnell

> Move impala-python initialization into the CMake build
> ------------------------------------------------------
>
>                 Key: IMPALA-10274
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10274
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 4.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>
> Currently, the impala-python virtualenv gets initialized on the first invocation of bin/impala-python. Most of the time, this happens when running bin/gen_build_version.py from buildall.sh. This is a serial part of the build, and the virtualenv initialization takes more than two minutes. 
> It would be better to use ordinary python for bin/gen_build_version.py (and any other python commands during the build) and initialize the virtualenv as a specific step in the CMake build. This would allow the virtualenv initialization to happen in parallel to the rest of the build, which saves multiple minutes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org