mirror of
https://github.com/apache/impala.git
synced 2025-12-19 18:12:08 -05:00
Initializing the impala-python virtualenv takes a couple minutes, so it is useful to do that in parallel to the rest of the build. This moves the impala-python initialization to its own step in the CMake build. It stops using impala-python for commands invoked from buildall.sh or the CMake build to avoid premature or concurrent initializations of impala-python. Then, it adds a dedicated step to initialize impala-python. Testing: - Ran a core job and a couple builds - Rebuilt and verified that impala-python is not reinitialized if it is already initialized Change-Id: Ieff51263c55bd234028fed7101c94b4a928590f0 Reviewed-on: http://gerrit.cloudera.org:8080/16607 Reviewed-by: Tim Armstrong <tarmstrong@cloudera.com> Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
16 KiB
16 KiB