[
https://issues.apache.org/jira/browse/IMPALA-10606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-10606.
------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Simplify impala-python virtualenv requirements files
> ----------------------------------------------------
>
> Key: IMPALA-10606
> URL: https://issues.apache.org/jira/browse/IMPALA-10606
> 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
>
>
> The impala-python virtualenv currently has complicated logic that can do
> multiple rounds of pip installs depending on whether the toolchain has been
> bootstrapped. For example, the packages in compile-requirements.txt are only
> installed if the toolchain GCC has been installed. The Kudu python client is
> only installed if Kudu has been downloaded. This was a workaround because
> bootstrap_toolchain.py required the impala-python virtualenv. The different
> stages allowed the basics to be installed, then bootstrap_toolchain.py can
> run, then the rest can be installed.
> The bootstrap_toolchain.py script no longer requires the impala-python
> virtualenv, so there is no need for such a complicated setup. The things
> bootstrapping the impala-python virtualenv can assume that the toolchain
> compiler is present. This would allow the requirements to be consolidated
> into a main requirements file that includes both compiled and non-compiled
> packages. A consolidated file makes it easier to update dependency versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
