[
https://issues.apache.org/jira/browse/IMPALA-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall reassigned IMPALA-8457:
----------------------------------------------
Assignee: (was: Thomas Tauber-Marshall)
> Fix python when Impala isn't fully built
> ----------------------------------------
>
> Key: IMPALA-8457
> URL: https://issues.apache.org/jira/browse/IMPALA-8457
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 3.3.0
> Reporter: Thomas Tauber-Marshall
> Priority: Critical
>
> A common pattern is to check out Impala, eg. in a Jenkins job, and then run
> Impala's functional python tests. If the tests are being run against a real
> cluster that has already been setup (as opposed to being run against the
> mini-cluster), it would be nice to be able to run any of our python tests
> without having to do a full build of Impala.
> This usually works, but occasionally gets broken eg. due to people adding
> imports of thrift structs to python files, since the thrift definitions
> aren't available without a full build. We dealt with this once recently in
> IMPALA-8199, and it has now cropped up again as a result of IMPALA-8158
> Going forward, I think a good solution would be to add a flag to buildall.sh,
> say '-testonly', that ensures that everything needed to run the python tests
> is done, eg. in this case something like 'make thrift-deps' should get run.
> We could incorporate running this into our pre-commit job to ensure that it
> doesn't get broken again in the future.
--
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
