mirror of
https://github.com/apache/impala.git
synced 2025-12-19 09:58:28 -05:00
60f8f87b09
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>
To install new packages: 1) Add your package to deps/requirements.txt, or deps/compiled-requirements.txt if the the package needs a C/C++ compiler to build . You should specify the version number using the "foo == x.y.z" notation so future upgrades can be done automatically. 2) Run deps/download_requirements, it will download the package to the deps dir. 3) Run the "impala-python" command, this should detect that requirements.txt changed and automatically rebuild the virtualenv. 4) Now in the python prompt, you should be able to import the new module. To upgrade a package: 1) Edit deps/requirement.txt to use the version you need. 2) Go to step 2 above.