[
https://issues.apache.org/jira/browse/IMPALA-10274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-10274.
------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> 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
> Fix For: Impala 4.0
>
>
> 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-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
