The source of truth for this is impala-config.sh: https://github.com/apache/impala/blob/master/bin/impala-config.sh#L173. Agree it could be useful to include it in the release notes or similar for a version.
Master supports building against a set of Hive 3 compatible version and a set of Hive 2 compatible versions. For various reasons (some historical, some practical) we're consuming CDH/CDP artifacts. It's not ideal and we'd like to be less dependent on that, but it is what it is at the moment. Impala's approach for a long time has been to pin dependency versions and then make sure we do a reasonable amount of integration testing to make sure that everything actually works together (it's pretty easy to get into dependency hell when you have so many complex dependencies that interact with each other). So probably you can mix and match versions of components to build against if you're adventurous, but we're not gonna guarantee anything. You can, of course, run against newer versions of dependencies if they're wire compatible. I don't know for sure what every other project's policy is (and whether it works as intended), but most of the ecosystem is forward-compatible so you can run against newer versions of the dependencies than you built against. - Tim On Wed, Jan 8, 2020 at 11:24 PM Lars Francke <[email protected]> wrote: > Hi Impala community, > > we've just looked at the Impala requirements (also in the docs) and are > wondering whether you have any specific requirements for your dependencies > (e.g. HBase, Hadoop et. al). > > Most/Some other projects have an "officially supported" list of versions - > we couldn't find any for Impala. > > Can you point me in the right direction? > > Thanks! > > Cheers, > Lars >
