Tim Armstrong 864a999569 use set-pythonpath only for impala-python ...

* Don't add PYTHONPATH to environment in impala-config.sh,
  it is done automatically by the impala-python script anyway.
  I think this is legacy from when we ran some things with
  the system python.
* Remove unnecessary set-pythonpath.sh invocations where all
  calls go via impala-python anyway.
* Remove impala-shell eggs from python path. All these packages
  are installed into the virtualenv.
* testdata path entry was not needed - it's imported via the root

Testing:
Ran core tests

Change-Id: Iff98eb261ab48c592e8d323aa409c6a65317b95a
Reviewed-on: http://gerrit.cloudera.org:8080/14238
Reviewed-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Tested-by: Tim Armstrong <tarmstrong@cloudera.com>

2019-09-24 16:46:31 +00:00

2.2 KiB

Executable File

Raw Blame History

View Raw