ashb opened a new pull request #8938:
URL: https://github.com/apache/airflow/pull/8938


   Debian Buster only ships with a JDK11, and Hive/Hadoop fails in odd,
   hard to debug ways (complains about metastore not being initalized,
   possibly related to the class loader issues.)
   
   Until we rip Hive out from the CI (replacing it with Hadoop in a seprate
   integration, only on for some builds) we'll have to stick with JRE8
   
   Our previous approach of installing openjdk-8 from Sid/Unstable started
   failing as Debian Sid has a new (and conflicting) version of GCC/libc.
   The adoptopenjdk package archive is designed for Buster so should be
   more resilient
   
   ---
   Make sure to mark the boxes below before creating PR: [x]
   
   - [x] Description above provides context of the change
   - [x] Unit tests coverage for changes (not needed for documentation changes)
   - [x] Target Github ISSUE in description if exists
   - [x] Commits follow "[How to write a good git commit 
message](http://chris.beams.io/posts/git-commit/)"
   - [x] Relevant documentation is updated including usage instructions.
   - [x] I will engage committers as explained in [Contribution Workflow 
Example](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#contribution-workflow-example).
   
   ---
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   Read the [Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)
 for more information.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to