[
https://issues.apache.org/jira/browse/IMPALA-4405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe McDonnell resolved IMPALA-4405.
-----------------------------------
Fix Version/s: Not Applicable
Resolution: Won't Fix
> Make it possible to do backwards/forwards compatibility testing of client
> binaries against a remote cluster
> -----------------------------------------------------------------------------------------------------------
>
> Key: IMPALA-4405
> URL: https://issues.apache.org/jira/browse/IMPALA-4405
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.8.0
> Reporter: David Knupp
> Priority: Major
> Fix For: Not Applicable
>
>
> Remote cluster testing currently is set up to run with whatever client
> binaries are installed on the client/test runner machine. It would be useful
> to be able to quickly test with various version of client binaries (by which
> is meant beeline, hbase shell, impala-shell, jdbc client, hadoop cmd line,
> and so on.)
> Options for getting different client binaries include:
> * Pull client binaries from an S3 bucket
> * Pull the client binaries from a repo directly
> * Add a feature to the Quasar test framework to run commands remotely. E.g.
> if we ran impala-shell on a remote host (via ssh), then we could test that
> impala shell worked OK on different platforms more easily, and then the local
> hadoop config woudn't be necessary. This may be too slow for the bulk of
> tests, but some compatibility tests could be run this way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
